State of PQC

Ciphers · hashes · protocols

History of transitions

Past moves from one cryptographic algorithm or protocol version to the next: when each was standardised, when it was attacked, when a deprecation date was set, when it was switched off, and where it is still in use. Each event carries the document it comes from. Last verified 28 Oct 2026.

Every transition

One row per transition, first event to last. A dot's colour is the kind of event; its name shows on hover and in the transition's own section.

19751980198519901995200020052010201520202025DES to AES15 Jan 1977: FIPS 46 (DES) published17 Jul 1998: EFF DES Cracker recovers a key in under three days19 Jan 1999: DES key recovered in 22 hours26 Nov 2001: FIPS 197 (AES) published19 May 2005: FIPS 46-3 (DES) withdrawnMar 2019: Three-key triple DES deprecated through 20231 Jan 2024: SP 800-67 (triple DES) withdrawnMD5 to SHA-2Apr 1992: RFC 1321 (MD5) published16 Aug 2004: Collisions for MD5 publishedMar 2011: RFC 6151 rules MD5 out for signaturesSHA-1 to SHA-217 Apr 1995: FIPS 180-1 (SHA-1) published1 Aug 2005: NIST records the first collision attack15 Mar 2006: Federal agencies must use SHA-2 for signatures after 2010Jan 2011: Signatures below 112 bits disallowed after 201316 Oct 2014: CA/Browser Forum ends SHA-1 issuance from 2016Jan 2017: Chrome 56 and Firefox 51 reject SHA-1 certificates23 Feb 2017: SHAttered9 May 2017: Edge and Internet Explorer 11 reject SHA-1 certificates7 Jan 2020: Chosen-prefix collision15 Dec 2022: NIST retires SHA-1 after 203028 Oct 2026: Git still names content by SHA-1RSA-1024 to RSA-2048Mar 1998: RFC 2313 (PKCS #1 v1.5) published1 Aug 2005: 1024-bit keys acceptable through 20107 Jan 2010: RSA-768 factoredJan 2011: 1024-bit signatures disallowed after 201322 Nov 2011: Baseline Requirements require 2048 bits for certificates valid past 20138 Sep 2014: Mozilla removes 1024-bit roots1 Oct 2016: DNS root zone signed with a 2048-bit ZSK10 Jun 2020: RSA-250 (829 bits) factoredRC4 in TLSJan 1999: RC4 cipher suites in TLS 1.013 Mar 2013: Plaintext recovery from RC4 keystream biases9 Oct 2013: 36.5% of surveyed servers still use RC4 with modern browsersFeb 2015: RFC 7465 prohibits RC4 in TLS26 Jan 2016: Firefox 44 stops offering RC4Feb 2016: Chrome removes RC49 Aug 2016: Edge and Internet Explorer 11 disable RC4SSL 3.0 and TLS 1.0 to TLS 1.318 Nov 1996: SSL 3.0 specificationJan 1999: RFC 2246 (TLS 1.0) publishedAug 2008: RFC 5246 (TLS 1.2) published14 Oct 2014: POODLE breaks SSL 3.0Jun 2015: RFC 7568 prohibits SSL 3.0Aug 2018: RFC 8446 (TLS 1.3) published15 Oct 2018: Browsers announce the end of TLS 1.0 and 1.1Mar 2020: Safari and Firefox disable TLS 1.0 and 1.1Mar 2021: RFC 8996 deprecates TLS 1.0 and 1.1WEP to WPA318 Nov 1997: IEEE 802.11-1997 published2001: Fluhrer2006: WPA2 required on all certified products2007: 104-bit WEP key recovered from under 4016 Mar 2015: Certified devices may no longer offer TKIP-only modesOct 2017: KRACK key reinstallation attacks on WPA225 Jun 2018: WPA3 introduced2020: WPA3 mandatory for new certified productsGSM A5/1 and COMP128Apr 1998: COMP128 broken10 May 1999: A5/1 implementation publishedApr 2001: MILENAGE example algorithm set publishedJul 2002: A5/3 specifiedMay 2004: GSMA proposes withdrawing A5/2 from handsetsDec 2009: A5/1 rainbow tables computed by volunteers15 Jun 2015: Singapore approves 2G closure for April 20171 Apr 2017: Singapore 2G networks closedApr 2021: Swisscom switches off 2G2025: GSMA guidance on 2G and 3G sunsetsMIFARE Classic28 Dec 2007: Crypto-1 partly reverse engineered7 Mar 2008: 48-bit keys recovered from MIFARE Classic18 Jul 2008: Court allows the attack to be publishedOct 2008: Dismantling MIFARE Classic published4 Jul 2018: Dutch public transport decides to replace MIFARE Classic28 Oct 2026: NXP still sells MIFARE ClassicSSH-1 and weak SSH algorithms12 Jun 1998: SSH-1 insertion attack on the CRC-32 checkJan 2006: RFC 4251 to 4254 (SSH-2) published11 Aug 2015: OpenSSH 7.0 disables SSH-1 and DSA keys by default19 Dec 2016: OpenSSH 7.4 removes the SSH-1 server26 Sep 2021: OpenSSH 8.8 disables SHA-1 RSA signatures1 Jul 2024: OpenSSH 9.8 announces DSA removal9 Apr 2025: OpenSSH 10.0 removes DSADNSSEC keys and algorithmsMar 2005: RFC 4033 to 4035 (DNSSEC) published15 Jul 2010: Root zone signed1 Oct 2016: Root ZSK increased to 2048 bits11 Oct 2018: First root KSK rolloverJun 2019: RFC 8624 marks SHA-1 signing algorithms not recommended24 Mar 2022: SHA-1 algorithms at about 7% of their peak deployment11 Oct 2026: Second root KSK rolloverKerberos DES and RC4 to AESJul 2005: RFC 4120 (Kerberos V5) published2008: AES in Windows KerberosJul 2012: RFC 6649 deprecates DES in KerberosOct 2018: RFC 8429 deprecates RC4 and triple DES in Kerberos8 Nov 2022: Windows makes AES the default session key type2024: Windows Server 2025 domain controllers stop issuing RC4 ticket-granting tickets14 Apr 2026: Domain controllers stop assuming RC4 by defaultIKEv1 to IKEv2, DES to AES in IPsecNov 1998: RFC 2409 (IKEv1) publishedDec 2005: RFC 4306 (IKEv2) publishedOct 2014: RFC 7296 (IKEv2) becomes the Internet StandardSep 2017: RFC 8247 bars DES from IKEv2Oct 2017: RFC 8221 sets triple DES to SHOULD NOT in ESPApr 2023: RFC 9395 moves IKEv1 to HistoricNSA Suite B to CNSA 2.02005: Suite B announced19 Aug 2015: NSA announces a transition to quantum-resistant algorithms7 Sep 2022: CNSA 2.0 published

Block ciphers

DES to AES

DES was a federal standard for 24 years before its key was shown to fall to a single machine in days. AES followed three years after that demonstration. Triple DES, the stopgap, stayed approved for another 22 years.

198019851990199520002005201020152020202515 Jan 1977: FIPS 46 (DES) publishedFIPS 46 (DES) published17 Jul 1998: EFF DES Cracker recovers a key in under three daysEFF DES Cracker recovers a key in under three days19 Jan 1999: DES key recovered in 22 hoursDES key recovered in 22 hours26 Nov 2001: FIPS 197 (AES) publishedFIPS 197 (AES) published19 May 2005: FIPS 46-3 (DES) withdrawnFIPS 46-3 (DES) withdrawnMar 2019: Three-key triple DES deprecated through 2023Three-key triple DES deprecated through 20231 Jan 2024: SP 800-67 (triple DES) withdrawnSP 800-67 (triple DES) withdrawn

22 years from the standard to the first attack; 21 from the attack to a deprecation date; 7 from the attack to the first switch-off.

DateEventKindSource
15 Jan 1977FIPS 46 (DES) publishedStandard publishedFIPS 46, Data Encryption Standard Date Published: January 15, 1977
17 Jul 1998EFF DES Cracker recovers a key in under three days A purpose-built machine wins RSA Laboratories' DES Challenge II.Attack publishedEFF DES Cracker project page It took the machine less than 3 days to complete the challenge, shattering the previous record of 39 days
19 Jan 1999DES key recovered in 22 hours DES Challenge IIIAttack publishedEFF DES Cracker project page in a record-breaking 22 hours and 15 minutes
26 Nov 2001FIPS 197 (AES) publishedStandard publishedFIPS 197, Advanced Encryption Standard Date Published: November 26, 2001
19 May 2005FIPS 46-3 (DES) withdrawnSwitched offFIPS 46-3, Data Encryption Standard Withdrawn on May 19, 2005.
Mar 2019Three-key triple DES deprecated through 2023 SP 800-131A Rev. 2 disallows it for encryption after 2023.Deprecation setSP 800-131A Rev. 2, Transitioning the Use of Cryptographic Algorithms and Key Lengths encryption using three-key TDEA is deprecated through December 31, 2023
1 Jan 2024SP 800-67 (triple DES) withdrawnSwitched offSP 800-67 Rev. 2, Recommendation for the Triple Data Encryption Algorithm Withdrawn on January 01, 2024

Sources

Hash functions

MD5 to SHA-2

MD5 was published in 1992 and collisions were found twelve years later. The IETF took another seven years to say in an RFC that MD5 is not acceptable for signatures.

199219941996199820002002200420062008201020122014201620182020202220242026Apr 1992: RFC 1321 (MD5) publishedRFC 1321 (MD5) published16 Aug 2004: Collisions for MD5 publishedCollisions for MD5 publishedMar 2011: RFC 6151 rules MD5 out for signaturesRFC 6151 rules MD5 out for signatures

12 years from the standard to the first attack; 7 from the attack to a deprecation date.

DateEventKindSource
Apr 1992RFC 1321 (MD5) publishedStandard publishedRFC 1321, The MD5 Message-Digest Algorithm This document describes the MD5 message-digest algorithm.
16 Aug 2004Collisions for MD5 published Wang, Feng, Lai and Yu, IACR ePrint 2004/199.Attack publishedCollisions for Hash Functions MD4, MD5, HAVAL-128 and RIPEMD
Mar 2011RFC 6151 rules MD5 out for signaturesDeprecation setRFC 6151, Updated Security Considerations for MD5 and HMAC-MD5 MD5 is no longer acceptable where collision resistance is required such as digital signatures.

Sources

Hash functions

SHA-1 to SHA-2

NIST set a 2010 end date for SHA-1 in signatures a year after the first attack was announced, and the web's certificate authorities stopped issuing SHA-1 certificates ten years after it. Browsers rejected the remaining certificates a month before the first real collision was published. Git still names content by SHA-1.

19941996199820002002200420062008201020122014201620182020202220242026202817 Apr 1995: FIPS 180-1 (SHA-1) publishedFIPS 180-1 (SHA-1) published1 Aug 2005: NIST records the first collision attackNIST records the first collision attack15 Mar 2006: Federal agencies must use SHA-2 for signatures after 2010Federal agencies must use SHA-2 for signatures after 2010Jan 2011: Signatures below 112 bits disallowed after 2013Signatures below 112 bits disallowed after 201316 Oct 2014: CA/Browser Forum ends SHA-1 issuance from 2016CA/Browser Forum ends SHA-1 issuance from 2016Jan 2017: Chrome 56 and Firefox 51 reject SHA-1 certificatesChrome 56 and Firefox 51 reject SHA-1 certificates23 Feb 2017: SHAtteredSHAttered9 May 2017: Edge and Internet Explorer 11 reject SHA-1 certificatesEdge and Internet Explorer 11 reject SHA-1 certificates7 Jan 2020: Chosen-prefix collisionChosen-prefix collision15 Dec 2022: NIST retires SHA-1 after 2030NIST retires SHA-1 after 203028 Oct 2026: Git still names content by SHA-1Git still names content by SHA-1

10 years from the standard to the first attack; 1 from the attack to a deprecation date; 11 from the attack to the first switch-off; still in use 32 years after the standard.

DateEventKindSource
17 Apr 1995FIPS 180-1 (SHA-1) publishedStandard publishedFIPS 180-1, Secure Hash Standard This standard specifies a Secure Hash Algorithm (SHA-1)
1 Aug 2005NIST records the first collision attack SP 800-57 puts SHA-1 collision resistance at 69 bits.Attack publishedSP 800-57 Part 1, Recommendation for Key Management (2005) SHA-1 has recently been demonstrated to provide less than 80 bits of security for digital signatures
15 Mar 2006Federal agencies must use SHA-2 for signatures after 2010Deprecation setNIST Policy on Hash Functions must use the SHA-2 family of hash functions for these applications after 2010
Jan 2011Signatures below 112 bits disallowed after 2013Deprecation setSP 800-131A, Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths (2011) After December 31, 2013, key lengths providing less than 112 bits of security strength shall not be used to generate digital signatures.
16 Oct 2014CA/Browser Forum ends SHA-1 issuance from 2016 Ballot 118.Deprecation setBallot 118, SHA-1 Sunset (passed) Effective 1 January 2016, CAs MUST NOT issue any new Subscriber certificates or Subordinate CA certificates using the SHA-1 hash algorithm.
Jan 2017Chrome 56 and Firefox 51 reject SHA-1 certificatesSwitched offSHA-1 certificates in Chrome we are planning to remove support for SHA-1 certificates in Chrome 56, which will be released to the stable channel
23 Feb 2017SHAtteredAttack publishedSHAttered showed the world the first real collision for the SHA-1 hash function
9 May 2017Edge and Internet Explorer 11 reject SHA-1 certificatesSwitched offCountdown to SHA-1 deprecation Microsoft Edge and Internet Explorer 11 will prevent sites that are protected with a SHA-1 certificate from loading
7 Jan 2020Chosen-prefix collision Leurent and Peyrin, IACR ePrint 2020/014.Attack publishedSHA-1 is a Shambles This proves that SHA-1 signatures now offers virtually no security in practice.
15 Dec 2022NIST retires SHA-1 after 2030Deprecation setNIST Policy on Hash Functions After 12/31/2030, any FIPS 140 validated cryptographic module that has SHA-1 as an approved algorithm
28 Oct 2026Git still names content by SHA-1 Page checked on this date; the transition to SHA-256 is documented but not complete.Still in useGit hash function transition It uses the SHA-1 hash function to name content.

Sources

Public keys

RSA-1024 to RSA-2048

NIST allowed 1024-bit keys through 2010 and disallowed them for signatures after 2013. The web PKI, browser root stores and the DNS root followed over the next three years. The largest key factored in public is still 829 bits.

199820002002200420062008201020122014201620182020202220242026Mar 1998: RFC 2313 (PKCS #1 v1.5) publishedRFC 2313 (PKCS #1 v1.5) published1 Aug 2005: 1024-bit keys acceptable through 20101024-bit keys acceptable through 20107 Jan 2010: RSA-768 factoredRSA-768 factoredJan 2011: 1024-bit signatures disallowed after 20131024-bit signatures disallowed after 201322 Nov 2011: Baseline Requirements require 2048 bits for certificates valid past 2013Baseline Requirements require 2048 bits for certificates valid past 20138 Sep 2014: Mozilla removes 1024-bit rootsMozilla removes 1024-bit roots1 Oct 2016: DNS root zone signed with a 2048-bit ZSKDNS root zone signed with a 2048-bit ZSK10 Jun 2020: RSA-250 (829 bits) factoredRSA-250 (829 bits) factored

12 years from the standard to the first attack; -4 from the attack to a deprecation date; 5 from the attack to the first switch-off.

DateEventKindSource
Mar 1998RFC 2313 (PKCS #1 v1.5) publishedStandard publishedRFC 2313, PKCS #1: RSA Encryption Version 1.5 This document describes a method for encrypting data using the RSA public-key cryptosystem.
1 Aug 20051024-bit keys acceptable through 2010 SP 800-57 sets 80 bits of strength as the minimum through 2010.Deprecation setSP 800-57 Part 1, Recommendation for Key Management (2005) Through 2010 (min. of 80 bits of strength)
7 Jan 2010RSA-768 factoredAttack publishedFactorization of a 768-bit RSA modulus This paper reports on the factorization of the 768-bit number RSA-768 by the number field sieve factoring method
Jan 20111024-bit signatures disallowed after 2013Deprecation setSP 800-131A, Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths (2011) After December 31, 2013, key lengths providing less than 112 bits of security strength shall not be used to generate digital signatures.
22 Nov 2011Baseline Requirements require 2048 bits for certificates valid past 2013 Version 1.0Deprecation setBaseline Requirements, Version 1.0 Minimum RSA modulus size (bits) 1024 2048
8 Sep 2014Mozilla removes 1024-bit rootsSwitched offPhasing out Certificates with 1024-bit RSA Keys after which no 1024-bit root certificates will be trusted to identify websites or software makers.
1 Oct 2016DNS root zone signed with a 2048-bit ZSKSwitched offRoot zone ZSK now 2048 bits (dns-operations list) As of 13:34 UTC on October 1, 2016 the root zone has been signed and published with a 2048-bit ZSK.
10 Jun 2020RSA-250 (829 bits) factoredAttack publishedComparing the difficulty of factorization and discrete logarithm: a 240-digit experiment The last page of this paper also reports on the factorization of RSA-250.

Sources

Stream ciphers

RC4 in TLS

RC4 was in the first TLS standard. When practical plaintext recovery was published in 2013 it protected about half of TLS traffic. The IETF prohibited it two years later and the three main browsers switched it off within the following eighteen months.

199820002002200420062008201020122014201620182020202220242026Jan 1999: RC4 cipher suites in TLS 1.0RC4 cipher suites in TLS 1.013 Mar 2013: Plaintext recovery from RC4 keystream biasesPlaintext recovery from RC4 keystream biases9 Oct 2013: 36.5% of surveyed servers still use RC4 with modern browsers36.5% of surveyed servers still use RC4 with modern browsersFeb 2015: RFC 7465 prohibits RC4 in TLSRFC 7465 prohibits RC4 in TLS26 Jan 2016: Firefox 44 stops offering RC4Firefox 44 stops offering RC4Feb 2016: Chrome removes RC4Chrome removes RC49 Aug 2016: Edge and Internet Explorer 11 disable RC4Edge and Internet Explorer 11 disable RC4

14 years from the standard to the first attack; 2 from the attack to a deprecation date; 3 from the attack to the first switch-off; still in use 15 years after the standard.

DateEventKindSource
Jan 1999RC4 cipher suites in TLS 1.0Standard publishedRFC 2246, The TLS Protocol Version 1.0 TLS_RSA_WITH_RC4_128_SHA
13 Mar 2013Plaintext recovery from RC4 keystream biases AlFardan, Bernstein, Paterson, Poettering and Schuldt.Attack publishedOn the Security of RC4 in TLS Around 50% of all TLS traffic is currently protected using the RC4 algorithm.
9 Oct 201336.5% of surveyed servers still use RC4 with modern browsersStill in useSSL Pulse: now tracking forward secrecy and RC4 But more than a third of servers (36.5%) actually use RC4 with at least one modern browser.
Feb 2015RFC 7465 prohibits RC4 in TLSDeprecation setRFC 7465, Prohibiting RC4 Cipher Suites TLS clients MUST NOT include RC4 cipher suites in the ClientHello message.
26 Jan 2016Firefox 44 stops offering RC4Switched offDeprecating the RC4 Cipher RC4 will no longer be offered by default in TLS fallback beginning with Firefox 44, set to be released on January 26, 2016.
Feb 2016Chrome removes RC4 Planned for a release around January or February 2016.Switched offTLS in Chrome Chrome will remove support for the RC4 cipher in a future release around January or February 2016.
9 Aug 2016Edge and Internet Explorer 11 disable RC4Switched offRC4 is now disabled in Microsoft Edge and Internet Explorer 11 RC4 is now disabled in Microsoft Edge and Internet Explorer 11

Sources

Protocols

SSL 3.0 and TLS 1.0 to TLS 1.3

SSL 3.0 lived 18 years before POODLE and was prohibited eight months after it. TLS 1.0 and 1.1 were disabled by the browsers in 2020, more than a decade after TLS 1.2 and a year before the RFC that formally deprecated them.

199619982000200220042006200820102012201420162018202020222024202618 Nov 1996: SSL 3.0 specificationSSL 3.0 specificationJan 1999: RFC 2246 (TLS 1.0) publishedRFC 2246 (TLS 1.0) publishedAug 2008: RFC 5246 (TLS 1.2) publishedRFC 5246 (TLS 1.2) published14 Oct 2014: POODLE breaks SSL 3.0POODLE breaks SSL 3.0Jun 2015: RFC 7568 prohibits SSL 3.0RFC 7568 prohibits SSL 3.0Aug 2018: RFC 8446 (TLS 1.3) publishedRFC 8446 (TLS 1.3) published15 Oct 2018: Browsers announce the end of TLS 1.0 and 1.1Browsers announce the end of TLS 1.0 and 1.1Mar 2020: Safari and Firefox disable TLS 1.0 and 1.1Safari and Firefox disable TLS 1.0 and 1.1Mar 2021: RFC 8996 deprecates TLS 1.0 and 1.1RFC 8996 deprecates TLS 1.0 and 1.1

18 years from the standard to the first attack; 1 from the attack to a deprecation date; 5 from the attack to the first switch-off.

DateEventKindSource
18 Nov 1996SSL 3.0 specification Published for the record as RFC 6101 in August 2011.Standard publishedRFC 6101, The Secure Sockets Layer (SSL) Protocol Version 3.0 the November 18, 1996, version of the protocol.
Jan 1999RFC 2246 (TLS 1.0) publishedStandard publishedRFC 2246, The TLS Protocol Version 1.0 This document specifies Version 1.0 of the Transport Layer Security (TLS) protocol.
Aug 2008RFC 5246 (TLS 1.2) publishedStandard publishedRFC 5246, The Transport Layer Security (TLS) Protocol Version 1.2 This document specifies Version 1.2 of the Transport Layer Security (TLS) protocol.
14 Oct 2014POODLE breaks SSL 3.0Attack publishedThis POODLE bites: exploiting the SSL 3.0 fallback In the coming months, we hope to remove support for SSL 3.0 completely from our client products.
Jun 2015RFC 7568 prohibits SSL 3.0Deprecation setRFC 7568, Deprecating Secure Sockets Layer Version 3.0 SSLv3 MUST NOT be used.
Aug 2018RFC 8446 (TLS 1.3) publishedStandard publishedRFC 8446, The Transport Layer Security (TLS) Protocol Version 1.3 This document specifies version 1.3 of the Transport Layer Security (TLS) protocol.
15 Oct 2018Browsers announce the end of TLS 1.0 and 1.1 ChromeDeprecation setModernizing Transport Security TLS 1.0 and 1.1 will be disabled altogether in Chrome 81.
Mar 2020Safari and Firefox disable TLS 1.0 and 1.1Switched offDeprecation of Legacy TLS 1.0 and 1.1 Versions Complete support will be removed from Safari in updates to Apple iOS and macOS beginning in March 2020.
Mar 2021RFC 8996 deprecates TLS 1.0 and 1.1Deprecation setRFC 8996, Deprecating TLS 1.0 and TLS 1.1 This document formally deprecates Transport Layer Security (TLS) versions 1.0 (RFC 2246) and 1.1 (RFC 4346).

Sources

Wireless

WEP to WPA3

WEP shipped in the first Wi-Fi standard and its RC4 key schedule was broken four years later. WPA2 became mandatory for certified products in 2006, but the Wi-Fi Alliance did not bar TKIP-only modes until 2015. WPA3 arrived in 2018, a year after KRACK.

199619982000200220042006200820102012201420162018202020222024202618 Nov 1997: IEEE 802.11-1997 publishedIEEE 802.11-1997 published2001: FluhrerFluhrer2006: WPA2 required on all certified productsWPA2 required on all certified products2007: 104-bit WEP key recovered from under 40104-bit WEP key recovered from under 4016 Mar 2015: Certified devices may no longer offer TKIP-only modesCertified devices may no longer offer TKIP-only modesOct 2017: KRACK key reinstallation attacks on WPA2KRACK key reinstallation attacks on WPA225 Jun 2018: WPA3 introducedWPA3 introduced2020: WPA3 mandatory for new certified productsWPA3 mandatory for new certified products

4 years from the standard to the first attack; 19 from the attack to a deprecation date; 14 from the attack to the first switch-off.

DateEventKindSource
18 Nov 1997IEEE 802.11-1997 published The standard that defines WEP.Standard publishedIEEE 802.11-1997 Published: 1997-11-18
2001FluhrerAttack publishedWeaknesses in the Key Scheduling Algorithm of RC4 RC4 is completely insecure in a common mode of operation which is used in the widely deployed Wired Equivalent Privacy protocol
2006WPA2 required on all certified productsStandard publishedTechnical Note: Removal of TKIP from Wi-Fi Devices Wi-Fi Alliance has required WPA2 on all Wi-Fi CERTIFIED products since 2006.
2007104-bit WEP key recovered from under 40 Tews, Weinmann and Pyshkin, IACR ePrint 2007/120.Attack publishedBreaking 104 bit WEP in less than 60 seconds We demonstrate an active attack on the WEP protocol that is able to recover a 104-bit WEP key using less than 40.000 frames in 50% of all cases.
16 Mar 2015Certified devices may no longer offer TKIP-only modesSwitched offTechnical Note: Removal of TKIP from Wi-Fi Devices Effective Date: March 16, 2015
Oct 2017KRACK key reinstallation attacks on WPA2Attack publishedKey Reinstallation Attacks We discovered serious weaknesses in WPA2, a protocol that secures all modern protected Wi-Fi networks.
25 Jun 2018WPA3 introducedStandard publishedWi-Fi Alliance introduces Wi-Fi CERTIFIED WPA3 security the next generation of Wi-Fi® security
2020WPA3 mandatory for new certified productsDeprecation setEight Wi-Fi trends expected in 2020 will become mandatory for all new Wi-Fi CERTIFIED™ products.

Sources

Mobile

GSM A5/1 and COMP128

The GSM SIM authentication algorithm was broken in 1998 and the A5/1 cipher was published the next year. Replacements were specified by 2002, but A5/1 stays in service until a 2G network is switched off, which is still happening operator by operator.

199820002002200420062008201020122014201620182020202220242026Apr 1998: COMP128 brokenCOMP128 broken10 May 1999: A5/1 implementation publishedA5/1 implementation publishedApr 2001: MILENAGE example algorithm set publishedMILENAGE example algorithm set publishedJul 2002: A5/3 specifiedA5/3 specifiedMay 2004: GSMA proposes withdrawing A5/2 from handsetsGSMA proposes withdrawing A5/2 from handsetsDec 2009: A5/1 rainbow tables computed by volunteersA5/1 rainbow tables computed by volunteers15 Jun 2015: Singapore approves 2G closure for April 2017Singapore approves 2G closure for April 20171 Apr 2017: Singapore 2G networks closedSingapore 2G networks closedApr 2021: Swisscom switches off 2GSwisscom switches off 2G2025: GSMA guidance on 2G and 3G sunsetsGSMA guidance on 2G and 3G sunsets

-3 years from the standard to the first attack; 6 from the attack to a deprecation date; 19 from the attack to the first switch-off; still in use 24 years after the standard.

DateEventKindSource
Apr 1998COMP128 brokenAttack publishedA pedagogical implementation of A5/1 (code header) In April of 1998, our group showed that COMP128, the algorithm used by the overwhelming majority of GSM providers
10 May 1999A5/1 implementation published Briceno, Goldberg and Wagner; verified against official test vectors.Attack publishedA pedagogical implementation of A5/1 (code header) which has been verified against official A5/1 test vectors
Apr 2001MILENAGE example algorithm set published 3GPP TS 35.205 V3.0.0.Standard published3GPP TS 35.205 V3.0.0 Specification of the MILENAGE Algorithm Set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*
Jul 2002A5/3 specified 3GPP TS 55.216 V1.0.0Standard publishedSP-020506, A5/3 and GEA3 specifications Specification of the A5/3 Encryption Algorithms for GSM and EDGE, and the GEA3 Encryption Algorithm for GPRS.
May 2004GSMA proposes withdrawing A5/2 from handsetsDeprecation setS3-040376, Withdrawal of A5/2 from handsets This input document proposes the withdrawal of A5/2 from handsets to reduce the threat of easily deriving the key Kc
Dec 2009A5/1 rainbow tables computed by volunteers Nohl and Paget, 26C3.Attack publishedGSM: SRSLY? (26C3) Add a weak cipher trivially breakable after a few months of distributed table generation
15 Jun 2015Singapore approves 2G closure for April 2017Deprecation setMNOs to close 2G networks from 1 April 2017 (Internet Archive copy) to close their 2G networks with effect from 1 April 2017.
1 Apr 2017Singapore 2G networks closedSwitched offMNOs to close 2G networks from 1 April 2017 (Internet Archive copy)
Apr 2021Swisscom switches off 2GSwitched offThe 2G network is history at Swisscom in mid-April 2021 it finally switched off the 2G technology.
2025GSMA guidance on 2G and 3G sunsetsStill in useNG.121 2G/3G Sunset Guidelines v3.0 Mobile operators are announcing 2/3G sunset

Sources

Smart cards

MIFARE Classic

The Crypto-1 cipher in MIFARE Classic cards was reverse engineered and broken within a year of the first public look at the chip. About 200 million cards were in use. Transport schemes took a decade to decide on replacements, and the chip is still sold.

20062008201020122014201620182020202220242026202828 Dec 2007: Crypto-1 partly reverse engineeredCrypto-1 partly reverse engineered7 Mar 2008: 48-bit keys recovered from MIFARE Classic48-bit keys recovered from MIFARE Classic18 Jul 2008: Court allows the attack to be publishedCourt allows the attack to be publishedOct 2008: Dismantling MIFARE Classic publishedDismantling MIFARE Classic published4 Jul 2018: Dutch public transport decides to replace MIFARE ClassicDutch public transport decides to replace MIFARE Classic28 Oct 2026: NXP still sells MIFARE ClassicNXP still sells MIFARE Classic

11 from the attack to a deprecation date.

DateEventKindSource
28 Dec 2007Crypto-1 partly reverse engineered Nohl and Plötz, 24C3.Attack published24C3: Mifare
7 Mar 200848-bit keys recovered from MIFARE ClassicAttack publishedSecurity flaw in MIFARE Classic allows the (48 bit) cryptographic keys to be relatively easily retrieved.
18 Jul 2008Court allows the attack to be published NXP's injunction request refused in Arnhem.Attack publishedCourt decision on publication (press release) may publish his article on the Mifare Classic Chip.
Oct 2008Dismantling MIFARE Classic published About 200 million cards in use.Attack publishedDismantling MIFARE Classic there are about 200 million mifare Classic tags in use around the world
4 Jul 2018Dutch public transport decides to replace MIFARE ClassicDeprecation setKamerstuk 23645 nr. 670 Deze nieuwe betaaltechniek zal de huidige techniek achter de OV-chipkaart (Mifare Classic) vervangen.
28 Oct 2026NXP still sells MIFARE Classic Page checked on this date; security-relevant applications are pointed to DESFire and Plus.Still in useMIFARE Classic product page

Sources

Protocols

SSH-1 and weak SSH algorithms

SSH-1's integrity check was broken in 1998 and SSH-2 was standardised in 2006. OpenSSH removed the SSH-1 server in 2016, SHA-1 RSA signatures in 2021 and DSA in 2025, ten years after first disabling it.

19982000200220042006200820102012201420162018202020222024202612 Jun 1998: SSH-1 insertion attack on the CRC-32 checkSSH-1 insertion attack on the CRC-32 checkJan 2006: RFC 4251 to 4254 (SSH-2) publishedRFC 4251 to 4254 (SSH-2) published11 Aug 2015: OpenSSH 7.0 disables SSH-1 and DSA keys by defaultOpenSSH 7.0 disables SSH-1 and DSA keys by default19 Dec 2016: OpenSSH 7.4 removes the SSH-1 serverOpenSSH 7.4 removes the SSH-1 server26 Sep 2021: OpenSSH 8.8 disables SHA-1 RSA signaturesOpenSSH 8.8 disables SHA-1 RSA signatures1 Jul 2024: OpenSSH 9.8 announces DSA removalOpenSSH 9.8 announces DSA removal9 Apr 2025: OpenSSH 10.0 removes DSAOpenSSH 10.0 removes DSA

-8 years from the standard to the first attack; 26 from the attack to a deprecation date; 17 from the attack to the first switch-off.

DateEventKindSource
12 Jun 1998SSH-1 insertion attack on the CRC-32 checkAttack publishedSSH insertion attack advisory (Internet Archive copy) current implementations rely on a 32 bit cyclic redundancy check to perform integrity checks after the decryption of an incoming packet.
Jan 2006RFC 4251 to 4254 (SSH-2) publishedStandard publishedRFC 4251, The Secure Shell (SSH) Protocol Architecture Secure Shell (SSH) is a protocol for secure remote login and other secure network services over an insecure network.
11 Aug 2015OpenSSH 7.0 disables SSH-1 and DSA keys by defaultSwitched offOpenSSH 7.0 release notes Support for ssh-dss, ssh-dss-cert-* host and user keys is disabled by default at run-time.
19 Dec 2016OpenSSH 7.4 removes the SSH-1 serverSwitched offOpenSSH 7.4 release notes This release removes server support for the SSH v.1 protocol.
26 Sep 2021OpenSSH 8.8 disables SHA-1 RSA signaturesSwitched offOpenSSH 8.8 release notes This release disables RSA signatures using the SHA-1 hash algorithm by default.
1 Jul 2024OpenSSH 9.8 announces DSA removalDeprecation setOpenSSH 9.8 release notes OpenSSH plans to remove support for the DSA signature algorithm in early 2025.
9 Apr 2025OpenSSH 10.0 removes DSASwitched offOpenSSH 10.0 release notes This release removes support for the weak DSA signature algorithm

Sources

Protocols

DNSSEC keys and algorithms

The root was signed five years after the DNSSEC RFCs, its ZSK grew to 2048 bits six years after that, and the KSK was first rolled in 2018. SHA-1 signing algorithms were marked not recommended in 2019 and had fallen to a small fraction of their peak by 2022.

2004200620082010201220142016201820202022202420262028Mar 2005: RFC 4033 to 4035 (DNSSEC) publishedRFC 4033 to 4035 (DNSSEC) published15 Jul 2010: Root zone signedRoot zone signed1 Oct 2016: Root ZSK increased to 2048 bitsRoot ZSK increased to 2048 bits11 Oct 2018: First root KSK rolloverFirst root KSK rolloverJun 2019: RFC 8624 marks SHA-1 signing algorithms not recommendedRFC 8624 marks SHA-1 signing algorithms not recommended24 Mar 2022: SHA-1 algorithms at about 7% of their peak deploymentSHA-1 algorithms at about 7% of their peak deployment11 Oct 2026: Second root KSK rolloverSecond root KSK rollover

-3 from the deprecation date to the first switch-off; still in use 17 years after the standard.

DateEventKindSource
Mar 2005RFC 4033 to 4035 (DNSSEC) publishedStandard publishedRFC 4033, DNS Security Introduction and Requirements DNS Security Introduction and Requirements
15 Jul 2010Root zone signedStandard publishedRoot DNSSEC status page (Internet Archive copy) ICANN publishes the root zone trust anchor and root operators begin to serve the signed root zone with actual keys
1 Oct 2016Root ZSK increased to 2048 bitsSwitched offRoot zone ZSK now 2048 bits (dns-operations list) As of 13:34 UTC on October 1, 2016 the root zone has been signed and published with a 2048-bit ZSK.
11 Oct 2018First root KSK rolloverSwitched offKSK Rollover 2018 On 11 October 2018, ICANN performed a Root Zone Domain Name System Security Extensions (DNSSEC) KSK rollover
Jun 2019RFC 8624 marks SHA-1 signing algorithms not recommended RSASHA1 and RSASHA1-NSEC3-SHA1 stay mandatory for validation.Deprecation setRFC 8624, Algorithm Implementation Requirements and Usage Guidance for DNSSEC RSASHA1 and RSASHA1-NSEC3-SHA1 are widely deployed, although the zones deploying it are recommended to switch to ECDSAP256SHA256
24 Mar 2022SHA-1 algorithms at about 7% of their peak deploymentStill in useDNSSEC algorithms for TLDs and everyone else these are down to approximately 7% of their peak deployment levels.
11 Oct 2026Second root KSK rolloverSwitched offICANN reports Root Zone KSK rollover completed as planned was completed on 11 October 2026.

Sources

Protocols

Kerberos DES and RC4 to AES

AES reached Kerberos in 2008. DES was deprecated by RFC in 2012 and RC4 in 2018, but Windows domain controllers kept assuming RC4 for accounts without a declared type until 2026.

2004200620082010201220142016201820202022202420262028Jul 2005: RFC 4120 (Kerberos V5) publishedRFC 4120 (Kerberos V5) published2008: AES in Windows KerberosAES in Windows KerberosJul 2012: RFC 6649 deprecates DES in KerberosRFC 6649 deprecates DES in KerberosOct 2018: RFC 8429 deprecates RC4 and triple DES in KerberosRFC 8429 deprecates RC4 and triple DES in Kerberos8 Nov 2022: Windows makes AES the default session key typeWindows makes AES the default session key type2024: Windows Server 2025 domain controllers stop issuing RC4 ticket-granting ticketsWindows Server 2025 domain controllers stop issuing RC4 ticket-granting tickets14 Apr 2026: Domain controllers stop assuming RC4 by defaultDomain controllers stop assuming RC4 by default

10 from the deprecation date to the first switch-off.

DateEventKindSource
Jul 2005RFC 4120 (Kerberos V5) publishedStandard publishedRFC 4120, The Kerberos Network Authentication Service (V5) This document provides an overview and specification of Version 5 of the Kerberos protocol
2008AES in Windows Kerberos Windows Vista and Windows Server 2008.Standard publishedKerberos Enhancements (Windows Vista and Windows Server 2008) enables the use of AES 128 and AES 256 encryption with the Kerberos authentication protocol.
Jul 2012RFC 6649 deprecates DES in KerberosDeprecation setRFC 6649, Deprecate DES, RC4-HMAC-EXP, and Other Weak Cryptographic Algorithms in Kerberos to deprecate the use of DES, RC4-HMAC-EXP, and other weak cryptographic algorithms in Kerberos.
Oct 2018RFC 8429 deprecates RC4 and triple DES in KerberosDeprecation setRFC 8429, Deprecate Triple-DES (3DES) and RC4 in Kerberos Kerberos implementations and deployments SHOULD NOT implement or deploy the RC4 encryption type RC4-HMAC(23).
8 Nov 2022Windows makes AES the default session key type KB5021131.Switched offKB5021131: How to manage the Kerberos protocol changes related to CVE-2022-37966 This update will set AES as the default encryption type for session keys on accounts that are not marked with a default encryption type already.
2024Windows Server 2025 domain controllers stop issuing RC4 ticket-granting ticketsSwitched offDetect and remediate RC4 usage in Kerberos Starting with Windows Server 2025, domain controllers don't issue RC4 Ticket Granting Tickets.
14 Apr 2026Domain controllers stop assuming RC4 by default Phased from January to July 2026.Switched offHow to manage Kerberos KDC usage of RC4 for service account ticket issuance (CVE-2026-20833) Windows updates released on and after April 14, 2026, change the Kerberos Key Distribution Center (KDC) default value for

Protocols

IKEv1 to IKEv2, DES to AES in IPsec

IKEv2 was published seven years after IKEv1. DES was barred from IKEv2 and ESP in 2017 and triple DES set to SHOULD NOT in ESP. IKEv1 itself was moved to Historic in 2023, 25 years after it was published.

199820002002200420062008201020122014201620182020202220242026Nov 1998: RFC 2409 (IKEv1) publishedRFC 2409 (IKEv1) publishedDec 2005: RFC 4306 (IKEv2) publishedRFC 4306 (IKEv2) publishedOct 2014: RFC 7296 (IKEv2) becomes the Internet StandardRFC 7296 (IKEv2) becomes the Internet StandardSep 2017: RFC 8247 bars DES from IKEv2RFC 8247 bars DES from IKEv2Oct 2017: RFC 8221 sets triple DES to SHOULD NOT in ESPRFC 8221 sets triple DES to SHOULD NOT in ESPApr 2023: RFC 9395 moves IKEv1 to HistoricRFC 9395 moves IKEv1 to Historic

6 from the deprecation date to the first switch-off.

DateEventKindSource
Nov 1998RFC 2409 (IKEv1) publishedStandard publishedRFC 2409, The Internet Key Exchange (IKE) This document describes a protocol using part of Oakley and part of SKEME in conjunction with ISAKMP to obtain authenticated keying material
Dec 2005RFC 4306 (IKEv2) publishedStandard publishedRFC 4306, Internet Key Exchange (IKEv2) Protocol This document describes version 2 of the Internet Key Exchange (IKE) protocol.
Oct 2014RFC 7296 (IKEv2) becomes the Internet StandardStandard publishedRFC 7296, Internet Key Exchange Protocol Version 2 (IKEv2) This document obsoletes RFC 5996, and includes all of the errata for it
Sep 2017RFC 8247 bars DES from IKEv2 Triple DES downgraded to MAY.Deprecation setRFC 8247, Algorithm Implementation Requirements and Usage Guidance for IKEv2 ENCR_DES can be brute-forced using off-the-shelf hardware. It provides no meaningful security whatsoever and, therefore, MUST NOT be implemented.
Oct 2017RFC 8221 sets triple DES to SHOULD NOT in ESPDeprecation setRFC 8221, Cryptographic Algorithm Implementation Requirements and Usage Guidance for ESP and AH ENCR_3DES status has been downgraded from MAY in [RFC7321] to SHOULD NOT.
Apr 2023RFC 9395 moves IKEv1 to HistoricSwitched offRFC 9395, Deprecation of the Internet Key Exchange Version 1 (IKEv1) Protocol and Obsoleted Algorithms Internet Key Exchange Version 1 (IKEv1) has been deprecated, and RFCs 2407, 2408, and 2409 have been moved to Historic status.

Government suites

NSA Suite B to CNSA 2.0

Suite B was announced in 2005 and NSA said it would move to quantum-resistant algorithms ten years later. CNSA 2.0 named the replacements in 2022 and expects the transition for national security systems to be complete by 2035.

2004200620082010201220142016201820202022202420262005: Suite B announcedSuite B announced19 Aug 2015: NSA announces a transition to quantum-resistant algorithmsNSA announces a transition to quantum-resistant algorithms7 Sep 2022: CNSA 2.0 publishedCNSA 2.0 published
DateEventKindSource
2005Suite B announcedStandard publishedFact Sheet NSA Suite B Cryptography (Internet Archive copy, 2005) the National Security Agency (NSA) announced Suite B Cryptography at the 2005 RSA Conference.
19 Aug 2015NSA announces a transition to quantum-resistant algorithmsDeprecation setSuite B Cryptography page as revised August 2015 (Internet Archive copy) IAD will initiate a transition to quantum resistant algorithms in the not too distant future.
7 Sep 2022CNSA 2.0 published Transition for national security systems complete by 2035.Deprecation setAnnouncing the Commercial National Security Algorithm Suite 2.0 NSA expects the transition to QR algorithms for NSS to be complete by 2035 in line with NSM-10.