From c046011388f509b5c3d94804796248d4dcb64cfc Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Thu, 6 Jun 2019 04:06:09 -0700 Subject: [PATCH] doc: improve DEP0090 text Edit text for "DEP0090: Invalid GCM authentication tag lengths" for clarity and branding. Invalid langths are "invalid" rather than "considered invalid". Refer to "Node.js v11.0.0" rather than "node v11.0.0". PR-URL: https://github.com/nodejs/node/pull/28097 Reviewed-By: Ruben Bridgewater Reviewed-By: Beth Griggs Reviewed-By: Colin Ihrig Reviewed-By: Trivikram Kamat --- doc/api/deprecations.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/api/deprecations.md b/doc/api/deprecations.md index 7f4273f82a0819..60ca92a84101c5 100644 --- a/doc/api/deprecations.md +++ b/doc/api/deprecations.md @@ -1809,10 +1809,10 @@ changes: Type: End-of-Life Node.js used to support all GCM authentication tag lengths which are accepted by -OpenSSL when calling [`decipher.setAuthTag()`][]. Beginning with node v11.0.0, -only authentication tag lengths of 128, 120, 112, 104, 96, 64, and 32 bits are -allowed. Authentication tags whose length is not included in this list are -considered invalid in compliance with [NIST SP 800-38D][]. +OpenSSL when calling [`decipher.setAuthTag()`][]. Beginning with Node.js +v11.0.0, only authentication tag lengths of 128, 120, 112, 104, 96, 64, and 32 +bits are allowed. Authentication tags of other lengths are invalid per +[NIST SP 800-38D][]. ### DEP0091: crypto.DEFAULT_ENCODING