pem_write_bio_x509 to string

Cryptography and SSL/TLS Toolkit

Pem_read_bio_privatekey.

pem_password_cb, PEM_read_bio_PrivateKey, PEM_read_PrivateKey, PEM_write_bio_PrivateKey, PEM_write_bio_PrivateKey_traditional, PEM_write_PrivateKey, PEM_write_bio_PKCS8PrivateKey, PEM_write_PKCS8PrivateKey, PEM_write_bio_PKCS8PrivateKey_nid, PEM_write_PKCS8PrivateKey_nid, PEM_read_bio_PUBKEY, PEM_read_PUBKEY, PEM_write_bio_PUBKEY, PEM_write_PUBKEY, PEM_read_bio_RSAPrivateKey, PEM_read_RSAPrivateKey, PEM_write_bio_RSAPrivateKey, PEM_write_RSAPrivateKey, PEM_read_bio_RSAPublicKey, PEM_read_RSAPublicKey, PEM_write_bio_RSAPublicKey, PEM_write_RSAPublicKey, PEM_read_bio_RSA_PUBKEY, PEM_read_RSA_PUBKEY, PEM_write_bio_RSA_PUBKEY, PEM_write_RSA_PUBKEY, PEM_read_bio_DSAPrivateKey, PEM_read_DSAPrivateKey, PEM_write_bio_DSAPrivateKey, PEM_write_DSAPrivateKey, PEM_read_bio_DSA_PUBKEY, PEM_read_DSA_PUBKEY, PEM_write_bio_DSA_PUBKEY, PEM_write_DSA_PUBKEY, PEM_read_bio_Parameters, PEM_write_bio_Parameters, PEM_read_bio_DSAparams, PEM_read_DSAparams, PEM_write_bio_DSAparams, PEM_write_DSAparams, PEM_read_bio_DHparams, PEM_read_DHparams, PEM_write_bio_DHparams, PEM_write_DHparams, PEM_read_bio_X509, PEM_read_X509, PEM_write_bio_X509, PEM_write_X509, PEM_read_bio_X509_AUX, PEM_read_X509_AUX, PEM_write_bio_X509_AUX, PEM_write_X509_AUX, PEM_read_bio_X509_REQ, PEM_read_X509_REQ, PEM_write_bio_X509_REQ, PEM_write_X509_REQ, PEM_write_bio_X509_REQ_NEW, PEM_write_X509_REQ_NEW, PEM_read_bio_X509_CRL, PEM_read_X509_CRL, PEM_write_bio_X509_CRL, PEM_write_X509_CRL, PEM_read_bio_PKCS7, PEM_read_PKCS7, PEM_write_bio_PKCS7, PEM_write_PKCS7 - PEM routines

DESCRIPTION

The PEM functions read or write structures in PEM format. In this sense PEM format is simply base64 encoded data surrounded by header lines.

For more details about the meaning of arguments see the PEM FUNCTION ARGUMENTS section.

Each operation has four functions associated with it. For brevity the term " TYPE functions" will be used below to collectively refer to the PEM_read_bio_TYPE(), PEM_read_TYPE(), PEM_write_bio_TYPE(), and PEM_write_TYPE() functions.

The PrivateKey functions read or write a private key in PEM format using an EVP_PKEY structure. The write routines use PKCS#8 private key format and are equivalent to PEM_write_bio_PKCS8PrivateKey().The read functions transparently handle traditional and PKCS#8 format encrypted and unencrypted keys.

PEM_write_bio_PrivateKey_traditional() writes out a private key in the "traditional" format with a simple private key marker and should only be used for compatibility with legacy programs.

PEM_write_bio_PKCS8PrivateKey() and PEM_write_PKCS8PrivateKey() write a private key in an EVP_PKEY structure in PKCS#8 EncryptedPrivateKeyInfo format using PKCS#5 v2.0 password based encryption algorithms. The cipher argument specifies the encryption algorithm to use: unlike some other PEM routines the encryption is applied at the PKCS#8 level and not in the PEM headers. If cipher is NULL then no encryption is used and a PKCS#8 PrivateKeyInfo structure is used instead.

PEM_write_bio_PKCS8PrivateKey_nid() and PEM_write_PKCS8PrivateKey_nid() also write out a private key as a PKCS#8 EncryptedPrivateKeyInfo however it uses PKCS#5 v1.5 or PKCS#12 encryption algorithms instead. The algorithm to use is specified in the nid parameter and should be the NID of the corresponding OBJECT IDENTIFIER (see NOTES section).

The PUBKEY functions process a public key using an EVP_PKEY structure. The public key is encoded as a SubjectPublicKeyInfo structure.

The RSAPrivateKey functions process an RSA private key using an RSA structure. The write routines uses traditional format. The read routines handles the same formats as the PrivateKey functions but an error occurs if the private key is not RSA.

The RSAPublicKey functions process an RSA public key using an RSA structure. The public key is encoded using a PKCS#1 RSAPublicKey structure.

The RSA_PUBKEY functions also process an RSA public key using an RSA structure. However, the public key is encoded using a SubjectPublicKeyInfo structure and an error occurs if the public key is not RSA.

The DSAPrivateKey functions process a DSA private key using a DSA structure. The write routines uses traditional format. The read routines handles the same formats as the PrivateKey functions but an error occurs if the private key is not DSA.

The DSA_PUBKEY functions process a DSA public key using a DSA structure. The public key is encoded using a SubjectPublicKeyInfo structure and an error occurs if the public key is not DSA.

The Parameters functions read or write key parameters in PEM format using an EVP_PKEY structure. The encoding depends on the type of key; for DSA key parameters, it will be a Dss-Parms structure as defined in RFC2459, and for DH key parameters, it will be a PKCS#3 DHparameter structure. These functions only exist for the BIO type .

The DSAparams functions process DSA parameters using a DSA structure. The parameters are encoded using a Dss-Parms structure as defined in RFC2459.

The DHparams functions process DH parameters using a DH structure. The parameters are encoded using a PKCS#3 DHparameter structure.

The X509 functions process an X509 certificate using an X509 structure. They will also process a trusted X509 certificate but any trust settings are discarded.

The X509_AUX functions process a trusted X509 certificate using an X509 structure.

The X509_REQ and X509_REQ_NEW functions process a PKCS#10 certificate request using an X509_REQ structure. The X509_REQ write functions use CERTIFICATE REQUEST in the header whereas the X509_REQ_NEW functions use NEW CERTIFICATE REQUEST (as required by some CAs). The X509_REQ read functions will handle either form so there are no X509_REQ_NEW read functions.

The X509_CRL functions process an X509 CRL using an X509_CRL structure.

The PKCS7 functions process a PKCS#7 ContentInfo using a PKCS7 structure.

PEM FUNCTION ARGUMENTS

The PEM functions have many common arguments.

The bp BIO parameter (if present) specifies the BIO to read from or write to.

The fp FILE parameter (if present) specifies the FILE pointer to read from or write to.

The PEM read functions all take an argument TYPE **x and return a TYPE * pointer. Where TYPE is whatever structure the function uses. If x is NULL then the parameter is ignored. If x is not NULL but *x is NULL then the structure returned will be written to *x . If neither x nor *x is NULL then an attempt is made to reuse the structure at *x (but see BUGS and EXAMPLES sections). Irrespective of the value of x a pointer to the structure is always returned (or NULL if an error occurred).

The PEM functions which write private keys take an enc parameter which specifies the encryption algorithm to use, encryption is done at the PEM level. If this parameter is set to NULL then the private key is written in unencrypted form.

The cb argument is the callback to use when querying for the pass phrase used for encrypted PEM structures (normally only private keys).

For the PEM write routines if the kstr parameter is not NULL then klen bytes at kstr are used as the passphrase and cb is ignored.

If the cb parameters is set to NULL and the u parameter is not NULL then the u parameter is interpreted as a null terminated string to use as the passphrase. If both cb and u are NULL then the default callback routine is used which will typically prompt for the passphrase on the current terminal with echoing turned off.

The default passphrase callback is sometimes inappropriate (for example in a GUI application) so an alternative can be supplied. The callback routine has the following form:

buf is the buffer to write the passphrase to. size is the maximum length of the passphrase (i.e. the size of buf). rwflag is a flag which is set to 0 when reading and 1 when writing. A typical routine will ask the user to verify the passphrase (for example by prompting for it twice) if rwflag is 1. The u parameter has the same value as the u parameter passed to the PEM routine. It allows arbitrary data to be passed to the callback by the application (for example a window handle in a GUI application). The callback must return the number of characters in the passphrase or -1 if an error occurred.

The old PrivateKey write routines are retained for compatibility. New applications should write private keys using the PEM_write_bio_PKCS8PrivateKey() or PEM_write_PKCS8PrivateKey() routines because they are more secure (they use an iteration count of 2048 whereas the traditional routines use a count of 1) unless compatibility with older versions of OpenSSL is important.

The PrivateKey read routines can be used in all applications because they handle all formats transparently.

A frequent cause of problems is attempting to use the PEM routines like this:

this is a bug because an attempt will be made to reuse the data at x which is an uninitialised pointer.

These functions make no assumption regarding the pass phrase received from the password callback. It will simply be treated as a byte sequence.

PEM ENCRYPTION FORMAT

These old PrivateKey routines use a non standard technique for encryption.

The private key (or other data) takes the following form:

The line beginning with Proc-Type contains the version and the protection on the encapsulated data. The line beginning DEK-Info contains two comma separated values: the encryption algorithm name as used by EVP_get_cipherbyname() and an initialization vector used by the cipher encoded as a set of hexadecimal digits. After those two lines is the base64-encoded encrypted data.

The encryption key is derived using EVP_BytesToKey(). The cipher's initialization vector is passed to EVP_BytesToKey() as the salt parameter. Internally, PKCS5_SALT_LEN bytes of the salt are used (regardless of the size of the initialization vector). The user's password is passed to EVP_BytesToKey() using the data and datal parameters. Finally, the library uses an iteration count of 1 for EVP_BytesToKey().

The key derived by EVP_BytesToKey() along with the original initialization vector is then used to decrypt the encrypted data. The iv produced by EVP_BytesToKey() is not utilized or needed, and NULL should be passed to the function.

The pseudo code to derive the key would look similar to:

The PEM read routines in some versions of OpenSSL will not correctly reuse an existing structure. Therefore, the following:

where x already contains a valid certificate, may not work, whereas:

is guaranteed to work.

RETURN VALUES

The read routines return either a pointer to the structure read or NULL if an error occurred.

The write routines return 1 for success or 0 for failure.

Although the PEM routines take several arguments in almost all applications most of them are set to 0 or NULL.

Read a certificate in PEM format from a BIO:

Alternative method:

Write a certificate to a BIO:

Write a private key (using traditional format) to a BIO using triple DES encryption, the pass phrase is prompted for:

Write a private key (using PKCS#8 format) to a BIO using triple DES encryption, using the pass phrase "hello":

Read a private key from a BIO using a pass phrase callback:

Skeleton pass phrase callback:

EVP_EncryptInit(3) , EVP_BytesToKey(3) , passphrase-encoding(7)

The old Netscape certificate sequences were no longer documented in OpenSSL 1.1.0; applications should use the PKCS7 standard instead as they will be formally deprecated in a future releases.

Copyright 2001-2020 The OpenSSL Project Authors. All Rights Reserved.

Licensed under the OpenSSL license (the "License"). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at https://www.openssl.org/source/license.html .

openssl C++研发之pem格式处理详解

一、PEM_writeXXX和EM_write_bio_XXX

在OpenSSL的 crypto/pem.h 头文件中， PEM_write_XXXX 和 PEM_write_bio_XXXX 系列函数用于将特定类型的数据写入文件或BIO（内存缓冲区）中，其中 XXXX 代表不同的数据类型。

这些函数的使用方式相似，通常接受一个文件指针（ FILE* ）或BIO指针（ BIO* ）作为参数，并将相应类型的数据写入到文件或BIO中。请根据需要选择合适的函数，并在使用时确保正确处理错误情况。

1.1 PEM_write_X509 / PEM_write_bio_X509

• 用于将X.509证书（X509结构体）写入文件或BIO中。

1.2 PEM_write_PrivateKey / PEM_write_bio_PrivateKey

• 用于将私钥（EVP_PKEY结构体）写入文件或BIO中。

1.3 PEM_write_PUBKEY / PEM_write_bio_PUBKEY

• 用于将公钥（EVP_PKEY结构体，通常是RSA、DSA、EC等密钥的公钥部分）写入文件或BIO中。

1.4. PEM_write_PKCS8PrivateKey / PEM_write_bio_PKCS8PrivateKey

• 用于将PKCS#8格式的私钥（EVP_PKEY结构体）写入文件或BIO中。

1.5. PEM_write_RSAPrivateKey / PEM_write_bio_RSAPrivateKey

• 用于将RSA私钥写入文件或BIO中。

1.6. PEM_write_RSAPublicKey / PEM_write_bio_RSAPublicKey

• 用于将RSA公钥写入文件或BIO中。

1.7. PEM_write_DSA / PEM_write_bio_DSA

• 用于将DSA密钥对（DSA结构体）写入文件或BIO中。

1.8. PEM_write_ECPrivateKey / PEM_write_bio_ECPrivateKey

• 用于将EC（椭圆曲线）私钥写入文件或BIO中。

1.9. PEM_write_EC_PUBKEY / PEM_write_bio_EC_PUBKEY

• 用于将EC公钥写入文件或BIO中。

二、PEM_writeXXX和EM_write_bio_XXX

PEM_readXXX 和 PEM_read_bio_XXX 是 OpenSSL 库中用于读取 PEM 格式数据的一组接口。这些接口被用于读取不同类型的 PEM 数据，例如证书、私钥等。下面简要说明这两组接口的作用：

2.1. PEM_readXXX

这组接口用于从文件或内存中读取 PEM 格式数据，其中 XXX 表示不同的数据类型，例如：

• PEM_read_RSAPrivateKey ：用于读取 RSA 私钥。
• PEM_read_RSAPublicKey ：用于读取 RSA 公钥。
• PEM_read_X509 ：用于读取 X.509 证书。

这些接口通常接受一个文件指针作为参数，用于从文件中读取 PEM 数据。

2.2. PEM_read_bio_XXX

这组接口也用于从文件或内存中读取 PEM 格式数据，但与 PEM_readXXX 不同的是， PEM_read_bio_XXX 接受一个 BIO 结构体作为参数，用于提供更灵活的输入源支持。 BIO 是 OpenSSL 中用于提供 I/O 抽象的结构体，它可以表示文件、内存等不同的数据源。

• PEM_read_bio_RSAPrivateKey ：用于从 BIO 中读取 RSA 私钥。
• PEM_read_bio_RSAPublicKey ：用于从 BIO 中读取 RSA 公钥。
• PEM_read_bio_X509 ：用于从 BIO 中读取 X.509 证书。

这里的例子演示了如何使用 PEM_read_RSAPrivateKey 和 PEM_read_bio_RSAPublicKey 从文件和内存中读取 RSA 密钥对。其他接口的使用方式类似，只需选择适当的接口和数据源类型。

“相关推荐”对你有帮助么？

请填写红包祝福语或标题

你的鼓励将是我创作的最大动力

您的余额不足，请更换扫码支付或 充值

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。 2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

zedwood.com

• code samples
• ascii table
• unicode table
• lightweight xlsx writer

C++ OpenSSL Parse X509 Certificate PEM

• Algorithms - HMAC
• Algorithms - MD2
• Algorithms - MD4
• Algorithms - MD5
• Algorithms - Password Based
• Algorithms - PKCS7
• Algorithms - PKCS11
• Algorithms - Poly1305
• Algorithms - PSA
• Algorithms - RIPEMD
• Algorithms - RSA
• Algorithms - SHA 128/224/256/384/512
• Algorithms - SipHash
• Algorithms - SRP

Source code

• signature.h
• wc_encrypt.h
• D. SSL/TLS Overview
• E. RFCs, Specifications, and Reference
• F. Error Codes
• G. Experimenting with Post-Quantum Cryptography
• H. wolfSSL Porting Guide

Functions Documentation

Function wolfssl_pem_write_bio_privatekey.

This function writes a key into a WOLFSSL_BIO structure in PEM format.

Parameters :

• bio WOLFSSL_BIO structure to get PEM buffer from.
• key key to convert to PEM format.
• cipher EVP cipher structure.
• passwd password.
• len length of password.
• cb password callback.
• arg optional argument.

See : wolfSSL_PEM_read_bio_X509_AUX

• SSL_SUCCESS upon success.
• SSL_FAILURE upon failure.

Updated on 2024-04-01 at 01:14:19 +0000

PEM_X509_INFO_read_ex, PEM_X509_INFO_read, PEM_X509_INFO_read_bio_ex, PEM_X509_INFO_read_bio - read PEM-encoded data structures into one or more X509_INFO objects

DESCRIPTION

PEM_X509_INFO_read_ex() loads the X509_INFO objects from a file fp .

PEM_X509_INFO_read() is similar to PEM_X509_INFO_read_ex() but uses the default (NULL) library context libctx and empty property query propq .

PEM_X509_INFO_read_bio_ex() loads the X509_INFO objects using a bio bp .

PEM_X509_INFO_read_bio() is similar to PEM_X509_INFO_read_bio_ex() but uses the default (NULL) library context libctx and empty property query propq .

Each of the loaded X509_INFO objects can contain a CRL, a certificate, and/or a private key. The elements are read sequentially, and as far as they are of different type than the elements read before, they are combined into the same X509_INFO object. The idea behind this is that if, for instance, a certificate is followed by a private key, the private key is supposed to correspond to the certificate.

If the input stack sk is NULL a new stack is allocated, else the given stack is extended.

The optional cb and u parameters can be used for providing a pass phrase needed for decrypting encrypted PEM structures (normally only private keys). See PEM_read_bio_PrivateKey(3) and passphrase-encoding(7) for details.

The library context libctx and property query propq are used for fetching algorithms from providers.

RETURN VALUES

PEM_X509_INFO_read_ex() , PEM_X509_INFO_read() , PEM_X509_INFO_read_bio_ex() and PEM_X509_INFO_read_bio() return a stack of X509_INFO objects or NULL on failure.

PEM_read_bio_ex(3) , PEM_read_bio_PrivateKey(3) , passphrase-encoding(7)

The functions PEM_X509_INFO_read_ex() and PEM_X509_INFO_read_bio_ex() were added in OpenSSL 3.0.

Copyright 2020-2022 The OpenSSL Project Authors. All Rights Reserved.

Licensed under the Apache License 2.0 (the "License"). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at https://www.openssl.org/source/license.html .

• LINUX / UNIX
• IOS / IPAD OS
• SWIFT/OBJECTIVE-C
• Download Free Trial
• VENDING MACHINE
• PRODUCTION LINE
• Download Free Trial Buy Now -->
• Miscellaneous

How to Use OpenSSL to Generate X.509 Certificate Request

•  OPENSSL
•  CERTIFICATE
•  SECURITY

In this tutorial, let’s learn how to use OpenSSL to generate X.509 certificate request.

Certificate signing request is a message sent from an applicant to a certificate authority, which usually includes:

• Country Name (2 letter code) [US]
• State or Province Name (full name) [BC]
• Locality Name (e.g., city) [Vancouver]
• Organization Name (e.g., company) [My Company Ltd]
• Organizational Unit Name (e.g., section)
• Common Name (e.g., your name or your server’s hostname)
• Email Address

Implementation Steps:

• Generate RSA key
• Set version
• Set subject
• Set public key
• Set sign key

Code & Result:

Search Blog Posts

Popular topics.

• Mobile Barcode Scanner
• Web Barcode Scanner
• Scanning Documents in Web
• Flutter Barcode Scanner
• Barcode Scan Benchmark
• Passport MRZ

Useful Links

• SOURCE CODE ON GITHUB

class OpenSSL::X509::Certificate

Implementation of an X.509 certificate as specified in RFC 5280. Provides access to a certificate’s attributes and allows certificates to be read from a string, but also supports the creation of new certificates from scratch.

Reading a certificate from a file ¶ ↑

Certificate is capable of handling DER-encoded certificates and certificates encoded in OpenSSL’s PEM format.

Saving a certificate to a file ¶ ↑

A certificate may be encoded in DER format

or in PEM format

X.509 certificates are associated with a private/public key pair, typically a RSA, DSA or ECC key (see also OpenSSL::PKey::RSA , OpenSSL::PKey::DSA and OpenSSL::PKey::EC ), the public key itself is stored within the certificate and can be accessed in form of an OpenSSL::PKey . Certificates are typically used to be able to associate some form of identity with a key pair, for example web servers serving pages over HTTPs use certificates to authenticate themselves to the user.

The public key infrastructure (PKI) model relies on trusted certificate authorities (“root CAs”) that issue these certificates, so that end users need to base their trust just on a selected few authorities that themselves again vouch for subordinate CAs issuing their certificates to end users.

The OpenSSL::X509 module provides the tools to set up an independent PKI, similar to scenarios where the ‘openssl’ command line tool is used for issuing certificates in a private PKI.

Creating a root CA certificate and an end-entity certificate ¶ ↑

First, we need to create a “self-signed” root certificate. To do so, we need to generate a key first. Please note that the choice of “1” as a serial number is considered a security flaw for real certificates. Secure choices are integers in the two-digit byte range and ideally not sequential but secure random numbers, steps omitted here to keep the example concise.

The next step is to create the end-entity certificate using the root CA certificate.

Public Class Methods

Read the chained certificates from the given input. Supports both PEM and DER encoded certificates.

PEM is a text format and supports more than one certificate.

DER is a binary format and only supports one certificate.

If the file is empty, or contains only unrelated data, an OpenSSL::X509::CertificateError exception will be raised.

Public Instance Methods

Compares the two certificates. Note that this takes into account all fields, not just the issuer name and the serial number.

Returns true if key is the corresponding private key to the Subject Public Key Information, false otherwise.

Verifies the signature of the certificate, with the public key key . key must be an instance of OpenSSL::PKey .

Skip Quicknav

• About Manpages
• Service Information

  / stretch / libssl-doc / PEM_read_X509_REQ(3ssl)

• language-indep link
• package tracker
• raw man page
• DESCRIPTION
• PEM FUNCTION ARGUMENTS
• PEM ENCRYPTION FORMAT
• RETURN CODES
• stretch 1.1.0j-1~deb9u1
• testing 1.1.1b-2
• unstable 1.1.1c-1

Scroll to navigation

DESCRIPTION ¶

For more details about the meaning of arguments see the PEM FUNCTION ARGUMENTS section.

Each operation has four functions associated with it. For clarity the term " foobar functions" will be used to collectively refer to the PEM_read_bio_foobar() , PEM_read_foobar() , PEM_write_bio_foobar() and PEM_write_foobar() functions.

The PrivateKey functions read or write a private key in PEM format using an EVP_PKEY structure. The write routines use PKCS#8 private key format and are equivalent to PEM_write_bio_PKCS8PrivateKey() .The read functions transparently handle traditional and PKCS#8 format encrypted and unencrypted keys.

PEM_write_bio_PrivateKey_traditional() writes out a private key in legacy "traditional" format.

PEM_write_bio_PKCS8PrivateKey() and PEM_write_PKCS8PrivateKey() write a private key in an EVP_PKEY structure in PKCS#8 EncryptedPrivateKeyInfo format using PKCS#5 v2.0 password based encryption algorithms. The cipher argument specifies the encryption algorithm to use: unlike some other PEM routines the encryption is applied at the PKCS#8 level and not in the PEM headers. If cipher is NULL then no encryption is used and a PKCS#8 PrivateKeyInfo structure is used instead.

PEM_write_bio_PKCS8PrivateKey_nid() and PEM_write_PKCS8PrivateKey_nid() also write out a private key as a PKCS#8 EncryptedPrivateKeyInfo however it uses PKCS#5 v1.5 or PKCS#12 encryption algorithms instead. The algorithm to use is specified in the nid parameter and should be the NID of the corresponding OBJECT IDENTIFIER (see NOTES section).

The PUBKEY functions process a public key using an EVP_PKEY structure. The public key is encoded as a SubjectPublicKeyInfo structure.

The RSAPrivateKey functions process an RSA private key using an RSA structure. The write routines uses traditional format. The read routines handles the same formats as the PrivateKey functions but an error occurs if the private key is not RSA.

The RSAPublicKey functions process an RSA public key using an RSA structure. The public key is encoded using a PKCS#1 RSAPublicKey structure.

The RSA_PUBKEY functions also process an RSA public key using an RSA structure. However the public key is encoded using a SubjectPublicKeyInfo structure and an error occurs if the public key is not RSA.

The DSAPrivateKey functions process a DSA private key using a DSA structure. The write routines uses traditional format. The read routines handles the same formats as the PrivateKey functions but an error occurs if the private key is not DSA.

The DSA_PUBKEY functions process a DSA public key using a DSA structure. The public key is encoded using a SubjectPublicKeyInfo structure and an error occurs if the public key is not DSA.

The DSAparams functions process DSA parameters using a DSA structure. The parameters are encoded using a Dss-Parms structure as defined in RFC2459.

The DHparams functions process DH parameters using a DH structure. The parameters are encoded using a PKCS#3 DHparameter structure.

The X509 functions process an X509 certificate using an X509 structure. They will also process a trusted X509 certificate but any trust settings are discarded.

The X509_AUX functions process a trusted X509 certificate using an X509 structure.

The X509_REQ and X509_REQ_NEW functions process a PKCS#10 certificate request using an X509_REQ structure. The X509_REQ write functions use CERTIFICATE REQUEST in the header whereas the X509_REQ_NEW functions use NEW CERTIFICATE REQUEST (as required by some CAs). The X509_REQ read functions will handle either form so there are no X509_REQ_NEW read functions.

The X509_CRL functions process an X509 CRL using an X509_CRL structure.

The PKCS7 functions process a PKCS#7 ContentInfo using a PKCS7 structure.

PEM FUNCTION ARGUMENTS ¶

The bp BIO parameter (if present) specifies the BIO to read from or write to.

The fp FILE parameter (if present) specifies the FILE pointer to read from or write to.

The PEM read functions all take an argument TYPE **x and return a TYPE * pointer. Where TYPE is whatever structure the function uses. If x is NULL then the parameter is ignored. If x is not NULL but *x is NULL then the structure returned will be written to *x . If neither x nor *x is NULL then an attempt is made to reuse the structure at *x (but see BUGS and EXAMPLES sections). Irrespective of the value of x a pointer to the structure is always returned (or NULL if an error occurred).

The PEM functions which write private keys take an enc parameter which specifies the encryption algorithm to use, encryption is done at the PEM level. If this parameter is set to NULL then the private key is written in unencrypted form.

The cb argument is the callback to use when querying for the pass phrase used for encrypted PEM structures (normally only private keys).

For the PEM write routines if the kstr parameter is not NULL then klen bytes at kstr are used as the passphrase and cb is ignored.

If the cb parameters is set to NULL and the u parameter is not NULL then the u parameter is interpreted as a null terminated string to use as the passphrase. If both cb and u are NULL then the default callback routine is used which will typically prompt for the passphrase on the current terminal with echoing turned off.

The default passphrase callback is sometimes inappropriate (for example in a GUI application) so an alternative can be supplied. The callback routine has the following form:

buf is the buffer to write the passphrase to. size is the maximum length of the passphrase (i.e. the size of buf). rwflag is a flag which is set to 0 when reading and 1 when writing. A typical routine will ask the user to verify the passphrase (for example by prompting for it twice) if rwflag is 1. The u parameter has the same value as the u parameter passed to the PEM routine. It allows arbitrary data to be passed to the callback by the application (for example a window handle in a GUI application). The callback must return the number of characters in the passphrase or -1 if an error occurred.

Read a certificate in PEM format from a BIO:

Alternative method:

Write a certificate to a BIO:

Write a private key (using traditional format) to a BIO using triple DES encryption, the pass phrase is prompted for:

Write a private key (using PKCS#8 format) to a BIO using triple DES encryption, using the pass phrase "hello":

Read a private key from a BIO using a pass phrase callback:

Skeleton pass phrase callback:

The PrivateKey read routines can be used in all applications because they handle all formats transparently.

A frequent cause of problems is attempting to use the PEM routines like this:

this is a bug because an attempt will be made to reuse the data at x which is an uninitialised pointer.

PEM ENCRYPTION FORMAT ¶

The private key (or other data) takes the following form:

The line beginning with Proc-Type contains the version and the protection on the encapsulated data. The line beginning DEK-Info contains two comma separated values: the encryption algorithm name as used by EVP_get_cipherbyname() and an initialization vector used by the cipher encoded as a set of hexadecimal digits. After those two lines is the base64-encoded encrypted data.

The encryption key is derived using EVP_BytesToKey() . The cipher's initialization vector is passed to EVP_BytesToKey() as the salt parameter. Internally, PKCS5_SALT_LEN bytes of the salt are used (regardless of the size of the initialization vector). The user's password is passed to EVP_BytesToKey() using the data and datal parameters. Finally, the library uses an iteration count of 1 for EVP_BytesToKey() .

The key derived by EVP_BytesToKey() along with the original initialization vector is then used to decrypt the encrypted data. The iv produced by EVP_BytesToKey() is not utilized or needed, and NULL should be passed to the function.

The pseudo code to derive the key would look similar to:

where x already contains a valid certificate, may not work, whereas:

is guaranteed to work.

RETURN CODES ¶

The write routines return 1 for success or 0 for failure.

COPYRIGHT ¶

Licensed under the OpenSSL license (the "License"). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at < https://www.openssl.org/source/license.html >.

debiman HEAD, see github.com/Debian/debiman . Found a problem? See the FAQ .

DESCRIPTION

Certificate extensions.

Powered by the Ubuntu Manpage Repository , file bugs in Launchpad

• x509-parser 0.16.0
• Docs.rs crate page
• MIT OR Apache-2.0
• Dependencies
• asn1-rs ^0.6.1 normal
• data-encoding ^2.2.1 normal
• der-parser ^9.0 normal
• lazy_static ^1.4 normal
• nom ^7.0 normal
• oid-registry ^0.7 normal
• ring ^0.17.7 normal optional
• rusticata-macros ^4.0 normal
• thiserror ^1.0.2 normal
• time ^0.3.20 normal
• 49.88% of the crate is documented
• i686-unknown-linux-gnu
• x86_64-unknown-linux-gnu
• Feature flags
• About docs.rs
• Privacy policy
• Rust website
• Standard Library API Reference
• Rust by Example
• The Cargo Guide
• Clippy Documentation

Module x509_parser :: pem

Decoding functions for PEM-encoded data

A PEM object is a container, which can store (amongst other formats) a public X.509 Certificate, or a CRL, etc. It contains only printable characters. PEM-encoded binary data is essentially a beginning and matching end tag that encloses base64-encoded binary data (see: https://en.wikipedia.org/wiki/Privacy-enhanced_Electronic_Mail ).

To parse a certificate in PEM format, first create the Pem object, then decode contents:

This is the most direct method to parse PEM data.

Another method to parse the certificate is to use parse_x509_pem :

Note that all methods require to store the Pem object in a variable, mainly because decoding the PEM object requires allocation of buffers, and that the lifetime of X.509 certificates will be bound to these buffers.

• Pem Representation of PEM data
• PemIterator Iterator over PEM-encapsulated blocks

Functions §

• parse_x509_pem Read a PEM-encoded structure, and decode the base64 data
• pem_to_der Deprecated

Search code, repositories, users, issues, pull requests...

Provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement . We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

using i2d_X509 ad input buffer CertCreateCertificateContext failed #17126

ghost commented Nov 24, 2021

t8m commented Nov 24, 2021

Sorry, something went wrong.

No branches or pull requests