diff options
Diffstat (limited to 'secure/lib/libcrypto/man/man3/EVP_PKEY_new.3')
| -rw-r--r-- | secure/lib/libcrypto/man/man3/EVP_PKEY_new.3 | 19 |
1 files changed, 11 insertions, 8 deletions
diff --git a/secure/lib/libcrypto/man/man3/EVP_PKEY_new.3 b/secure/lib/libcrypto/man/man3/EVP_PKEY_new.3 index 6d478bb51674..f43d0853c48a 100644 --- a/secure/lib/libcrypto/man/man3/EVP_PKEY_new.3 +++ b/secure/lib/libcrypto/man/man3/EVP_PKEY_new.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 "EVP_PKEY_NEW 3ossl" -.TH EVP_PKEY_NEW 3ossl 2025-09-30 3.5.4 OpenSSL +.TH EVP_PKEY_NEW 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 @@ -173,7 +176,7 @@ algorithm type). .PP \&\fBEVP_PKEY_new_raw_private_key()\fR does the same as \&\fBEVP_PKEY_new_raw_private_key_ex()\fR except that the default library context and -default property query are used instead. If \fIe\fR is non-NULL then the new +default property query are used instead. If \fIe\fR is non\-NULL then the new \&\fBEVP_PKEY\fR structure is associated with the engine \fIe\fR. The \fItype\fR argument indicates what kind of key this is. The value should be a NID for a public key algorithm that supports raw private keys, i.e. one of \fBEVP_PKEY_X25519\fR, @@ -233,7 +236,7 @@ and \&\fBML\-KEM\-512\fR, \&\fBML\-KEM\-768\fR and \&\fBML\-KEM\-1024\fR -keys, which don't have legacy numeric \fINID\fR assignments, but their raw form is +keys, which don\*(Aqt have legacy numeric \fINID\fR assignments, but their raw form is nevertheless available. .PP \&\fBEVP_PKEY_get_raw_public_key()\fR fills the buffer provided by \fIpub\fR with raw @@ -256,14 +259,14 @@ and \&\fBML\-KEM\-512\fR, \&\fBML\-KEM\-768\fR and \&\fBML\-KEM\-1024\fR -keys, which don't have legacy numeric \fINID\fR assignments, but their raw form is +keys, which don\*(Aqt have legacy numeric \fINID\fR assignments, but their raw form is nevertheless available. .PP \&\fBEVP_PKEY_new_CMAC_key()\fR works in the same way as \fBEVP_PKEY_new_raw_private_key()\fR except it is only for the \fBEVP_PKEY_CMAC\fR algorithm type. In addition to the raw private key data, it also takes a cipher algorithm to be used during creation of a CMAC in the \fBcipher\fR argument. The cipher should be a standard -encryption-only cipher. For example AEAD and XTS ciphers should not be used. +encryption\-only cipher. For example AEAD and XTS ciphers should not be used. .PP Applications should use the \fBEVP_MAC\fR\|(3) API instead and set the \fBOSSL_MAC_PARAM_CIPHER\fR parameter on the \fBEVP_MAC_CTX\fR object @@ -279,7 +282,7 @@ key to this empty structure use the appropriate functions described in \&\fBEVP_PKEY_set1_EC_KEY\fR\|(3) for legacy key types implemented in internal OpenSSL providers. .PP -For fully provider-managed key types (see \fBprovider\-keymgmt\fR\|(7)), +For fully provider\-managed key types (see \fBprovider\-keymgmt\fR\|(7)), possibly implemented in external providers, use functions such as \&\fBEVP_PKEY_set1_encoded_public_key\fR\|(3) or \fBEVP_PKEY_fromdata\fR\|(3) to populate key data. @@ -336,7 +339,7 @@ The documentation of \fBEVP_PKEY\fR was amended in OpenSSL 3.0 to allow there to be the private part of the keypair without the public part, where this was previously implied to be disallowed. .PP -Support for \fBML-DSA\fR and \fBML-KEM\fR was added in OpenSSL 3.5. +Support for \fBML\-DSA\fR and \fBML\-KEM\fR was added in OpenSSL 3.5. .SH COPYRIGHT .IX Header "COPYRIGHT" Copyright 2002\-2025 The OpenSSL Project Authors. All Rights Reserved. |