diff options
| author | Pauli <paul.dale@oracle.com> | 2019-09-25 20:30:09 +1000 |
|---|---|---|
| committer | Pauli <paul.dale@oracle.com> | 2019-09-26 07:10:41 +1000 |
| commit | 560ac83b0bfc6f871075c5891f96c5817b06f7b8 (patch) | |
| tree | 4c4d2a61da8ace0198efd9a1246eca288dd94888 | |
| parent | f49a65d09c09b3309b711518664b8ee973ec4b96 (diff) | |
KDF section 3 clean up
Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/10011)
| -rw-r--r-- | doc/man3/EVP_KDF.pod | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/man3/EVP_KDF.pod b/doc/man3/EVP_KDF.pod index afd4b6cc6c..9fa9a17d48 100644 --- a/doc/man3/EVP_KDF.pod +++ b/doc/man3/EVP_KDF.pod @@ -198,7 +198,7 @@ The length must never exceed what can be given with a B<size_t>. Memory-hard password-based KDF algorithms, such as scrypt, use an amount of memory that depends on the load factors provided as input. -For those KDF implementations that support it, this uint64_t parameter sets +For those KDF implementations that support it, this B<uint64_t> parameter sets an upper limit on the amount of memory that may be consumed while performing a key derivation. If this memory usage limit is exceeded because the load factors are chosen |