diff options
Diffstat (limited to 'doc/man7')
-rw-r--r-- | doc/man7/EVP_KDF_HKDF.pod | 2 | ||||
-rw-r--r-- | doc/man7/EVP_KDF_SCRYPT.pod | 2 | ||||
-rw-r--r-- | doc/man7/EVP_KDF_SS.pod | 6 | ||||
-rw-r--r-- | doc/man7/EVP_KDF_SSHKDF.pod | 2 | ||||
-rw-r--r-- | doc/man7/EVP_KDF_TLS1_PRF.pod | 2 | ||||
-rw-r--r-- | doc/man7/EVP_KDF_X942.pod | 2 | ||||
-rw-r--r-- | doc/man7/EVP_KDF_X963.pod | 2 | ||||
-rw-r--r-- | doc/man7/Ed25519.pod | 2 | ||||
-rw-r--r-- | doc/man7/SM2.pod | 2 | ||||
-rw-r--r-- | doc/man7/X25519.pod | 2 | ||||
-rw-r--r-- | doc/man7/bio.pod | 2 |
11 files changed, 11 insertions, 15 deletions
diff --git a/doc/man7/EVP_KDF_HKDF.pod b/doc/man7/EVP_KDF_HKDF.pod index 2188b136f1..c511c7c705 100644 --- a/doc/man7/EVP_KDF_HKDF.pod +++ b/doc/man7/EVP_KDF_HKDF.pod @@ -126,7 +126,7 @@ the intermediate fixed-length pseudorandom key otherwise an error will occur. For that mode, the fixed output size can be looked up by calling EVP_KDF_size() after setting the mode and digest on the C<EVP_KDF_CTX>. -=head1 EXAMPLE +=head1 EXAMPLES This example derives 10 bytes using SHA-256 with the secret key "secret", salt value "salt" and info value "label": diff --git a/doc/man7/EVP_KDF_SCRYPT.pod b/doc/man7/EVP_KDF_SCRYPT.pod index a44dc63dec..aa50164e06 100644 --- a/doc/man7/EVP_KDF_SCRYPT.pod +++ b/doc/man7/EVP_KDF_SCRYPT.pod @@ -78,7 +78,7 @@ A context for scrypt can be obtained by calling: The output length of an scrypt key derivation is specified via the B<keylen> parameter to the L<EVP_KDF_derive(3)> function. -=head1 EXAMPLE +=head1 EXAMPLES This example derives a 64-byte long test vector using scrypt with the password "password", salt "NaCl" and N = 1024, r = 8, p = 16. diff --git a/doc/man7/EVP_KDF_SS.pod b/doc/man7/EVP_KDF_SS.pod index 958089d24a..5c56fbd1b0 100644 --- a/doc/man7/EVP_KDF_SS.pod +++ b/doc/man7/EVP_KDF_SS.pod @@ -102,7 +102,7 @@ EVP_KDF_CTX *kctx = EVP_KDF_CTX_new_id(EVP_KDF_SS); The output length of an SSKDF is specified via the C<keylen> parameter to the L<EVP_KDF_derive(3)> function. -=head1 EXAMPLE +=head1 EXAMPLES This example derives 10 bytes using H(x) = SHA-256, with the secret key "secret" and fixedinfo value "label": @@ -127,8 +127,6 @@ and fixedinfo value "label": EVP_KDF_CTX_free(kctx); -=head1 EXAMPLE - This example derives 10 bytes using H(x) = HMAC(SHA-256), with the secret key "secret", fixedinfo value "label" and salt "salt": @@ -158,8 +156,6 @@ fixedinfo value "label" and salt "salt": EVP_KDF_CTX_free(kctx); -=head1 EXAMPLE - This example derives 10 bytes using H(x) = KMAC128(x,salt,outlen), with the secret key "secret" fixedinfo value "label", salt of "salt" and KMAC outlen of 20: diff --git a/doc/man7/EVP_KDF_SSHKDF.pod b/doc/man7/EVP_KDF_SSHKDF.pod index e233e86f03..04a646c866 100644 --- a/doc/man7/EVP_KDF_SSHKDF.pod +++ b/doc/man7/EVP_KDF_SSHKDF.pod @@ -120,7 +120,7 @@ to obtain the requisite length is not meaningful. The caller must allocate a buffer of the desired length, and pass that buffer to the L<EVP_KDF_derive(3)> function along with the desired length. -=head1 EXAMPLE +=head1 EXAMPLES This example derives an 8 byte IV using SHA-256 with a 1K "key" and appropriate "xcghash" and "session_id" values: diff --git a/doc/man7/EVP_KDF_TLS1_PRF.pod b/doc/man7/EVP_KDF_TLS1_PRF.pod index 4c73139546..02331ece5e 100644 --- a/doc/man7/EVP_KDF_TLS1_PRF.pod +++ b/doc/man7/EVP_KDF_TLS1_PRF.pod @@ -97,7 +97,7 @@ an error will occur. The output length of the PRF is specified by the C<keylen> parameter to the EVP_KDF_derive() function. -=head1 EXAMPLE +=head1 EXAMPLES This example derives 10 bytes using SHA-256 with the secret key "secret" and seed value "seed": diff --git a/doc/man7/EVP_KDF_X942.pod b/doc/man7/EVP_KDF_X942.pod index df93e861f9..644cad8cbe 100644 --- a/doc/man7/EVP_KDF_X942.pod +++ b/doc/man7/EVP_KDF_X942.pod @@ -90,7 +90,7 @@ EVP_KDF_CTX *kctx = EVP_KDF_CTX_new_id(EVP_KDF_X942); The output length of an X942KDF is specified via the C<keylen> parameter to the L<EVP_KDF_derive(3)> function. -=head1 EXAMPLE +=head1 EXAMPLES This example derives 24 bytes, with the secret key "secret" and a random user keying material: diff --git a/doc/man7/EVP_KDF_X963.pod b/doc/man7/EVP_KDF_X963.pod index 77b878f6ba..130c9235a9 100644 --- a/doc/man7/EVP_KDF_X963.pod +++ b/doc/man7/EVP_KDF_X963.pod @@ -81,7 +81,7 @@ EVP_KDF_CTX *kctx = EVP_KDF_CTX_new_id(EVP_KDF_X963); The output length of an X963KDF is specified via the C<keylen> parameter to the L<EVP_KDF_derive(3)> function. -=head1 EXAMPLE +=head1 EXAMPLES This example derives 10 bytes, with the secret key "secret" and sharedinfo value "label": diff --git a/doc/man7/Ed25519.pod b/doc/man7/Ed25519.pod index 12bc64b3f7..8269f2feaa 100644 --- a/doc/man7/Ed25519.pod +++ b/doc/man7/Ed25519.pod @@ -53,7 +53,7 @@ Ed25519 and Ed448 can be tested within L<speed(1)> application since version 1.1 Valid algorithm names are B<ed25519>, B<ed448> and B<eddsa>. If B<eddsa> is specified, then both Ed25519 and Ed448 are benchmarked. -=head1 EXAMPLE +=head1 EXAMPLES This example generates an B<ED25519> private key and writes it to standard output in PEM format: diff --git a/doc/man7/SM2.pod b/doc/man7/SM2.pod index 05c8a345fd..31f58db416 100644 --- a/doc/man7/SM2.pod +++ b/doc/man7/SM2.pod @@ -41,7 +41,7 @@ done by calling: And normally there is no need to pass a B<pctx> parameter to EVP_DigestSignInit() or EVP_DigestVerifyInit() in such a scenario. -=head1 EXAMPLE +=head1 EXAMPLES This example demonstrates the calling sequence for using an B<EVP_PKEY> to verify a message with the SM2 signature algorithm and the SM3 hash algorithm: diff --git a/doc/man7/X25519.pod b/doc/man7/X25519.pod index 7f0bdff276..6af40c6afe 100644 --- a/doc/man7/X25519.pod +++ b/doc/man7/X25519.pod @@ -37,7 +37,7 @@ X25519 or X448 public keys can be set directly using L<EVP_PKEY_new_raw_public_key(3)> or loaded from a SubjectPublicKeyInfo structure in a PEM file using L<PEM_read_bio_PUBKEY(3)> (or similar function). -=head1 EXAMPLE +=head1 EXAMPLES This example generates an B<X25519> private key and writes it to standard output in PEM format: diff --git a/doc/man7/bio.pod b/doc/man7/bio.pod index 18f1125045..bc1fb1e45e 100644 --- a/doc/man7/bio.pod +++ b/doc/man7/bio.pod @@ -52,7 +52,7 @@ pointer to a BIO_METHOD. There is a naming convention for such functions: a source/sink BIO is normally called BIO_s_*() and a filter BIO BIO_f_*(); -=head1 EXAMPLE +=head1 EXAMPLES Create a memory BIO: |