From 67b7ad3b6791eca041d35fdb1b2db72d4d98798f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tobias=20Nie=C3=9Fen?= Date: Sun, 21 Jan 2018 14:13:38 +0100 Subject: [PATCH] doc: use PBKDF2 in text MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Use upper case variant in text in compliance with RFC 2898. PR-URL: https://github.com/nodejs/node/pull/18279 Reviewed-By: Michaël Zasso Reviewed-By: Vladimir Kurchatkin Reviewed-By: Ruben Bridgewater --- 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 644ebbeb56cbfd..5813b44a71a396 100644 --- a/doc/api/crypto.md +++ b/doc/api/crypto.md @@ -1196,7 +1196,7 @@ password always creates the same key. The low iteration count and non-cryptographically secure hash algorithm allow passwords to be tested very rapidly. -In line with OpenSSL's recommendation to use pbkdf2 instead of +In line with OpenSSL's recommendation to use PBKDF2 instead of [`EVP_BytesToKey`][] it is recommended that developers derive a key and IV on their own using [`crypto.pbkdf2()`][] and to use [`crypto.createCipheriv()`][] to create the `Cipher` object. Users should not use ciphers with counter mode @@ -1258,7 +1258,7 @@ password always creates the same key. The low iteration count and non-cryptographically secure hash algorithm allow passwords to be tested very rapidly. -In line with OpenSSL's recommendation to use pbkdf2 instead of +In line with OpenSSL's recommendation to use PBKDF2 instead of [`EVP_BytesToKey`][] it is recommended that developers derive a key and IV on their own using [`crypto.pbkdf2()`][] and to use [`crypto.createDecipheriv()`][] to create the `Decipher` object.