aboutsummaryrefslogtreecommitdiff
path: root/secure/lib/libcrypto/man/man3/PEM_read_bio_PrivateKey.3
diff options
context:
space:
mode:
Diffstat (limited to 'secure/lib/libcrypto/man/man3/PEM_read_bio_PrivateKey.3')
-rw-r--r--secure/lib/libcrypto/man/man3/PEM_read_bio_PrivateKey.319
1 files changed, 11 insertions, 8 deletions
diff --git a/secure/lib/libcrypto/man/man3/PEM_read_bio_PrivateKey.3 b/secure/lib/libcrypto/man/man3/PEM_read_bio_PrivateKey.3
index 26322737087e..376ecef7bc97 100644
--- a/secure/lib/libcrypto/man/man3/PEM_read_bio_PrivateKey.3
+++ b/secure/lib/libcrypto/man/man3/PEM_read_bio_PrivateKey.3
@@ -1,5 +1,5 @@
.\" -*- mode: troff; coding: utf-8 -*-
-.\" Automatically generated by Pod::Man 5.0102 (Pod::Simple 3.45)
+.\" Automatically generated by Pod::Man v6.0.2 (Pod::Simple 3.45)
.\"
.\" Standard preamble:
.\" ========================================================================
@@ -52,10 +52,13 @@
. \}
.\}
.rr rF
+.\"
+.\" Required to disable full justification in groff 1.23.0.
+.if n .ds AD l
.\" ========================================================================
.\"
.IX Title "PEM_READ_BIO_PRIVATEKEY 3ossl"
-.TH PEM_READ_BIO_PRIVATEKEY 3ossl 2025-09-30 3.5.4 OpenSSL
+.TH PEM_READ_BIO_PRIVATEKEY 3ossl 2026-04-07 3.5.6 OpenSSL
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -341,12 +344,12 @@ key is not DSA.
.PP
The \fBParameters\fR 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
+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. \fIThese functions
only exist for the \fR\f(BIBIO\fR\fI type\fR.
.PP
The \fBDSAparams\fR functions process DSA parameters using a DSA
-structure. The parameters are encoded using a Dss-Parms structure
+structure. The parameters are encoded using a Dss\-Parms structure
as defined in RFC2459.
.PP
The \fBDHparams\fR functions process DH parameters using a DH
@@ -485,17 +488,17 @@ The private key (or other data) takes the following form:
\& \-\-\-\-\-END RSA PRIVATE KEY\-\-\-\-\-
.Ve
.PP
-The line beginning with \fIProc-Type\fR contains the version and the
-protection on the encapsulated data. The line beginning \fIDEK-Info\fR
+The line beginning with \fIProc\-Type\fR contains the version and the
+protection on the encapsulated data. The line beginning \fIDEK\-Info\fR
contains two comma separated values: the encryption algorithm name as
used by \fBEVP_get_cipherbyname()\fR 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.
.PP
-The encryption key is derived using \fBEVP_BytesToKey()\fR. The cipher's
+The encryption key is derived using \fBEVP_BytesToKey()\fR. The cipher\*(Aqs
initialization vector is passed to \fBEVP_BytesToKey()\fR as the \fIsalt\fR
parameter. Internally, \fBPKCS5_SALT_LEN\fR bytes of the salt are used
-(regardless of the size of the initialization vector). The user's
+(regardless of the size of the initialization vector). The user\*(Aqs
password is passed to \fBEVP_BytesToKey()\fR using the \fIdata\fR and \fIdatal\fR
parameters. Finally, the library uses an iteration count of 1 for
\&\fBEVP_BytesToKey()\fR.