|PEM_BYTES_READ_BIO(3)||Library Functions Manual||PEM_BYTES_READ_BIO(3)|
read a PEM-encoded data structure from a BIO
**pdata, long *plen, char
**pnm, const char *name, BIO
*in_bp, pem_password_cb *cb,
reads and PEM decodes the first object of type name
(e.g. RSA PRIVATE KEY, CERTIFICATE, etc.) from in_bp.
If multiple PEM-encoded data structures are present in the same stream, it
skips non-matching data types and continues reading. Before reading each PEM
object, lines not starting with "-----BEGIN " are also skipped;
see PEM_read_bio(3) for details of
The PEM header may indicate that the following data is encrypted; if so, the data is decrypted, optionally using cb and u, as described in pem_password_cb(3).
Some data types have compatibility aliases, such as a file
containing X509 CERTIFICATE matching a request for the deprecated type
CERTIFICATE. The actual type indicated by the file is returned in
*pnm if pnm is
NULL. The caller must free the storage pointed
to by *pnm.
The returned data is the DER-encoded form of the requested type, in *pdata with length *plen. The caller must free the storage pointed to by *pdata.
PEM_bytes_read_bio() returns 1 for success
or 0 for failure.
PEM_R_NO_START_LINE"no start line"
PEM_R_NOT_PROC_TYPE"not proc type"
PEM_R_NOT_DEK_INFO"not dek info"
PEM_R_BAD_IV_CHARS"bad iv chars"
PEM_R_BAD_PASSWORD_READ"bad password read"
Additional types of errors can result from PEM_read_bio(3).
RFC 1421: Privacy Enhancement for Internet Electronic Mail (PEM), Part I
PEM_bytes_read_bio() first appeared in
OpenSSL 0.9.7 and has been available since OpenBSD
|July 23, 2020||OpenBSD-current|