Commit 5ad0d04
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: #28097
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>1 parent 9074f9b commit 5ad0d04
1 file changed
Lines changed: 4 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1809,10 +1809,10 @@ changes: | |||
| 1809 | 1809 | Type: End-of-Life | |
| 1810 | 1810 | ||
| 1811 | 1811 | Node.js used to support all GCM authentication tag lengths which are accepted by | |
| 1812 | - OpenSSL when calling [`decipher.setAuthTag()`][]. Beginning with node v11.0.0, | ||
| 1813 | - only authentication tag lengths of 128, 120, 112, 104, 96, 64, and 32 bits are | ||
| 1814 | - allowed. Authentication tags whose length is not included in this list are | ||
| 1815 | - considered invalid in compliance with [NIST SP 800-38D][]. | ||
| 1812 | + OpenSSL when calling [`decipher.setAuthTag()`][]. Beginning with Node.js | ||
| 1813 | + v11.0.0, only authentication tag lengths of 128, 120, 112, 104, 96, 64, and 32 | ||
| 1814 | + bits are allowed. Authentication tags of other lengths are invalid per | ||
| 1815 | + [NIST SP 800-38D][]. | ||
| 1816 | 1816 | ||
| 1817 | 1817 | <a id="DEP0091"></a> | |
| 1818 | 1818 | ### DEP0091: crypto.DEFAULT_ENCODING | |
0 commit comments