From 560c18238b5d692feeb472192c0d5f7cfb2c2075 Mon Sep 17 00:00:00 2001 From: Will Clark Date: Thu, 7 Dec 2017 13:06:41 +0100 Subject: [PATCH] doc: correct pbkdf2 salt length recommendation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit According to the linked document: "The length of the randomly-generated portion of the salt shall be at least 128 bits." [NIST SP 800-132] PR-URL: https://github.com/nodejs/node/pull/17524 Reviewed-By: Tobias Nießen Reviewed-By: Colin Ihrig Reviewed-By: Daniel Bevenius Reviewed-By: Ben Noordhuis Reviewed-By: Luigi Pinca --- doc/api/crypto.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/api/crypto.md b/doc/api/crypto.md index 078f485880c824..1f11f443a9e2ce 100644 --- a/doc/api/crypto.md +++ b/doc/api/crypto.md @@ -1622,7 +1622,7 @@ higher the number of iterations, the more secure the derived key will be, but will take a longer amount of time to complete. The `salt` should also be as unique as possible. It is recommended that the -salts are random and their lengths are greater than 16 bytes. See +salts are random and their lengths are at least 16 bytes. See [NIST SP 800-132][] for details. Example: @@ -1686,7 +1686,7 @@ higher the number of iterations, the more secure the derived key will be, but will take a longer amount of time to complete. The `salt` should also be as unique as possible. It is recommended that the -salts are random and their lengths are greater than 16 bytes. See +salts are random and their lengths are at least 16 bytes. See [NIST SP 800-132][] for details. Example: