1
Fork 0
mirror of git://git.sv.gnu.org/emacs.git synced 2025-12-06 06:20:55 -08:00

Improve nsm-protocol-check--3des-cipher docstring

* lisp/net/nsm.el (nsm-protocol-check--3des-cipher): Update
docstring to reflect current NIST policy.
This commit is contained in:
Stefan Kangas 2023-10-25 01:06:27 +02:00
parent 04215e616f
commit 6dca3a8eab

View file

@ -550,14 +550,14 @@ Due to its use of 64-bit block size, it is known that a
ciphertext collision is highly likely when 2^32 blocks are ciphertext collision is highly likely when 2^32 blocks are
encrypted with the same key bundle under 3-key 3DES. Practical encrypted with the same key bundle under 3-key 3DES. Practical
birthday attacks of this kind have been demonstrated by Sweet32[1]. birthday attacks of this kind have been demonstrated by Sweet32[1].
As such, NIST is in the process of disallowing its use in TLS[2]. As such, NIST has disallowed its use after December 31, 2023[2].
[1]: Bhargavan, Leurent (2016). \"On the Practical (In-)Security of [1]: Bhargavan, Leurent (2016). \"On the Practical (In-)Security of
64-bit Block Ciphers Collision Attacks on HTTP over TLS and 64-bit Block Ciphers Collision Attacks on HTTP over TLS and
OpenVPN\", `https://sweet32.info/' OpenVPN\", `https://sweet32.info/'
[2]: NIST Information Technology Laboratory (Jul 2017). \"Update to [2]: National Institute of Standards and Technology (Mar 2019).
Current Use and Deprecation of TDEA\", \"Transitioning the Use of Cryptographic Algorithms and Key
`https://csrc.nist.gov/News/2017/Update-to-Current-Use-and-Deprecation-of-TDEA'" Lengths\", `https://doi.org/10.6028/NIST.SP.800-131Ar2'"
(let ((cipher (plist-get status :cipher))) (let ((cipher (plist-get status :cipher)))
(and (string-match "\\b3DES\\b" cipher) (and (string-match "\\b3DES\\b" cipher)
(format-message (format-message