From: Pauli Date: Wed, 25 Sep 2019 10:30:09 +0000 (+1000) Subject: KDF section 3 clean up X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=560ac83b0bfc6f871075c5891f96c5817b06f7b8;p=openssl KDF section 3 clean up Reviewed-by: Richard Levitte (Merged from https://github.com/openssl/openssl/pull/10011) --- 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. 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 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