From 985d180855d1d57f64ee213ed72fb460328f53f0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tobias=20Nie=C3=9Fen?= Date: Wed, 11 Apr 2018 13:52:51 +0200 Subject: [PATCH] doc: move support for invalid GCM tags to EOL PR-URL: https://github.com/nodejs/node/pull/17825 Refs: https://github.com/nodejs/node/issues/17523 Reviewed-By: Ben Noordhuis Reviewed-By: Joyee Cheung Reviewed-By: James M Snell --- doc/api/deprecations.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/doc/api/deprecations.md b/doc/api/deprecations.md index 0e91514cfd240e..6689f03a25edef 100644 --- a/doc/api/deprecations.md +++ b/doc/api/deprecations.md @@ -823,14 +823,13 @@ same as the legacy assert but it will always use strict equality checks. ### DEP0090: Invalid GCM authentication tag lengths -Type: Runtime +Type: End-of-Life -Node.js supports all GCM authentication tag lengths which are accepted by -OpenSSL when calling [`decipher.setAuthTag()`][]. This behavior will change in -a future version at which point only authentication tag lengths of 128, 120, -112, 104, 96, 64, and 32 bits will be allowed. Authentication tags whose length -is not included in this list will be considered invalid in compliance with -[NIST SP 800-38D][]. +Node.js used to support all GCM authentication tag lengths which are accepted by +OpenSSL when calling [`decipher.setAuthTag()`][]. Beginning with node REPLACEME, +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][]. ### DEP0091: crypto.DEFAULT_ENCODING