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.
- Standard published
- Attack published
- Deprecation set
- Switched off
- Still in use
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.
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.
| Date | Event | Kind | Source |
|---|---|---|---|
| 15 Jan 1977 | FIPS 46 (DES) published | Standard published | FIPS 46, Data Encryption Standard Date Published: January 15, 1977 |
| 17 Jul 1998 | EFF DES Cracker recovers a key in under three days A purpose-built machine wins RSA Laboratories' DES Challenge II. | Attack published | EFF 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 1999 | DES key recovered in 22 hours DES Challenge III | Attack published | EFF DES Cracker project page in a record-breaking 22 hours and 15 minutes |
| 26 Nov 2001 | FIPS 197 (AES) published | Standard published | FIPS 197, Advanced Encryption Standard Date Published: November 26, 2001 |
| 19 May 2005 | FIPS 46-3 (DES) withdrawn | Switched off | FIPS 46-3, Data Encryption Standard Withdrawn on May 19, 2005. |
| Mar 2019 | Three-key triple DES deprecated through 2023 SP 800-131A Rev. 2 disallows it for encryption after 2023. | Deprecation set | SP 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 2024 | SP 800-67 (triple DES) withdrawn | Switched off | SP 800-67 Rev. 2, Recommendation for the Triple Data Encryption Algorithm Withdrawn on January 01, 2024 |
Sources
- FIPS 46, Data Encryption Standard NBS · 15 Jan 1977 · checked 28 Oct 2026
- EFF DES Cracker project page Electronic Frontier Foundation · 19 Jan 1999 · checked 28 Oct 2026
- FIPS 197, Advanced Encryption Standard NIST · 26 Nov 2001 · checked 28 Oct 2026
- FIPS 46-3, Data Encryption Standard NIST · 25 Oct 1999 · checked 28 Oct 2026
- SP 800-131A Rev. 2, Transitioning the Use of Cryptographic Algorithms and Key Lengths NIST · Mar 2019 · checked 28 Oct 2026
- SP 800-67 Rev. 2, Recommendation for the Triple Data Encryption Algorithm NIST · Nov 2017 · checked 28 Oct 2026
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.
12 years from the standard to the first attack; 7 from the attack to a deprecation date.
| Date | Event | Kind | Source |
|---|---|---|---|
| Apr 1992 | RFC 1321 (MD5) published | Standard published | RFC 1321, The MD5 Message-Digest Algorithm This document describes the MD5 message-digest algorithm. |
| 16 Aug 2004 | Collisions for MD5 published Wang, Feng, Lai and Yu, IACR ePrint 2004/199. | Attack published | Collisions for Hash Functions MD4, MD5, HAVAL-128 and RIPEMD |
| Mar 2011 | RFC 6151 rules MD5 out for signatures | Deprecation set | RFC 6151, Updated Security Considerations for MD5 and HMAC-MD5 MD5 is no longer acceptable where collision resistance is required such as digital signatures. |
Sources
- RFC 1321, The MD5 Message-Digest Algorithm IETF · Apr 1992 · checked 28 Oct 2026
- Collisions for Hash Functions MD4, MD5, HAVAL-128 and RIPEMD IACR ePrint 2004/199 · 16 Aug 2004 · checked 28 Oct 2026
- RFC 6151, Updated Security Considerations for MD5 and HMAC-MD5 IETF · Mar 2011 · checked 28 Oct 2026
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.
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.
| Date | Event | Kind | Source |
|---|---|---|---|
| 17 Apr 1995 | FIPS 180-1 (SHA-1) published | Standard published | FIPS 180-1, Secure Hash Standard This standard specifies a Secure Hash Algorithm (SHA-1) |
| 1 Aug 2005 | NIST records the first collision attack SP 800-57 puts SHA-1 collision resistance at 69 bits. | Attack published | SP 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 2006 | Federal agencies must use SHA-2 for signatures after 2010 | Deprecation set | NIST Policy on Hash Functions must use the SHA-2 family of hash functions for these applications after 2010 |
| Jan 2011 | Signatures below 112 bits disallowed after 2013 | Deprecation set | SP 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 2014 | CA/Browser Forum ends SHA-1 issuance from 2016 Ballot 118. | Deprecation set | Ballot 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 2017 | Chrome 56 and Firefox 51 reject SHA-1 certificates | Switched off | SHA-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 2017 | SHAttered | Attack published | SHAttered showed the world the first real collision for the SHA-1 hash function |
| 9 May 2017 | Edge and Internet Explorer 11 reject SHA-1 certificates | Switched off | Countdown 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 2020 | Chosen-prefix collision Leurent and Peyrin, IACR ePrint 2020/014. | Attack published | SHA-1 is a Shambles This proves that SHA-1 signatures now offers virtually no security in practice. |
| 15 Dec 2022 | NIST retires SHA-1 after 2030 | Deprecation set | NIST Policy on Hash Functions After 12/31/2030, any FIPS 140 validated cryptographic module that has SHA-1 as an approved algorithm |
| 28 Oct 2026 | Git still names content by SHA-1 Page checked on this date; the transition to SHA-256 is documented but not complete. | Still in use | Git hash function transition It uses the SHA-1 hash function to name content. |
Sources
- FIPS 180-1, Secure Hash Standard NIST · 17 Apr 1995 · checked 28 Oct 2026
- SP 800-57 Part 1, Recommendation for Key Management (2005) NIST · 1 Aug 2005 · checked 28 Oct 2026
- NIST Policy on Hash Functions NIST · 15 Dec 2022 · checked 28 Oct 2026
- SP 800-131A, Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths (2011) NIST · Jan 2011 · checked 28 Oct 2026
- Ballot 118, SHA-1 Sunset (passed) CA/Browser Forum · 16 Oct 2014 · checked 28 Oct 2026
- SHA-1 certificates in Chrome Chromium project · Jan 2017 · checked 28 Oct 2026
- SHAttered Google and CWI · 23 Feb 2017 · checked 28 Oct 2026
- Countdown to SHA-1 deprecation Microsoft Edge team · 26 Apr 2017 · checked 28 Oct 2026
- SHA-1 is a Shambles IACR ePrint 2020/014 · 7 Jan 2020 · checked 28 Oct 2026
- Git hash function transition Git project · 28 Oct 2026 · checked 28 Oct 2026
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.
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.
| Date | Event | Kind | Source |
|---|---|---|---|
| Mar 1998 | RFC 2313 (PKCS #1 v1.5) published | Standard published | RFC 2313, PKCS #1: RSA Encryption Version 1.5 This document describes a method for encrypting data using the RSA public-key cryptosystem. |
| 1 Aug 2005 | 1024-bit keys acceptable through 2010 SP 800-57 sets 80 bits of strength as the minimum through 2010. | Deprecation set | SP 800-57 Part 1, Recommendation for Key Management (2005) Through 2010 (min. of 80 bits of strength) |
| 7 Jan 2010 | RSA-768 factored | Attack published | Factorization 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 2011 | 1024-bit signatures disallowed after 2013 | Deprecation set | SP 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 2011 | Baseline Requirements require 2048 bits for certificates valid past 2013 Version 1.0 | Deprecation set | Baseline Requirements, Version 1.0 Minimum RSA modulus size (bits) 1024 2048 |
| 8 Sep 2014 | Mozilla removes 1024-bit roots | Switched off | Phasing 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 2016 | DNS root zone signed with a 2048-bit ZSK | Switched off | Root 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 2020 | RSA-250 (829 bits) factored | Attack published | Comparing 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
- RFC 2313, PKCS #1: RSA Encryption Version 1.5 IETF · Mar 1998 · checked 28 Oct 2026
- SP 800-57 Part 1, Recommendation for Key Management (2005) NIST · 1 Aug 2005 · checked 28 Oct 2026
- Factorization of a 768-bit RSA modulus IACR ePrint 2010/006 · 7 Jan 2010 · checked 28 Oct 2026
- SP 800-131A, Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths (2011) NIST · Jan 2011 · checked 28 Oct 2026
- Baseline Requirements, Version 1.0 CA/Browser Forum · 22 Nov 2011 · checked 28 Oct 2026
- Phasing out Certificates with 1024-bit RSA Keys Mozilla · 8 Sep 2014 · checked 28 Oct 2026
- Root zone ZSK now 2048 bits (dns-operations list) Verisign · 1 Oct 2016 · checked 28 Oct 2026
- Comparing the difficulty of factorization and discrete logarithm: a 240-digit experiment IACR ePrint 2020/697 · 10 Jun 2020 · checked 28 Oct 2026
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.
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.
| Date | Event | Kind | Source |
|---|---|---|---|
| Jan 1999 | RC4 cipher suites in TLS 1.0 | Standard published | RFC 2246, The TLS Protocol Version 1.0 TLS_RSA_WITH_RC4_128_SHA |
| 13 Mar 2013 | Plaintext recovery from RC4 keystream biases AlFardan, Bernstein, Paterson, Poettering and Schuldt. | Attack published | On the Security of RC4 in TLS Around 50% of all TLS traffic is currently protected using the RC4 algorithm. |
| 9 Oct 2013 | 36.5% of surveyed servers still use RC4 with modern browsers | Still in use | SSL 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 2015 | RFC 7465 prohibits RC4 in TLS | Deprecation set | RFC 7465, Prohibiting RC4 Cipher Suites TLS clients MUST NOT include RC4 cipher suites in the ClientHello message. |
| 26 Jan 2016 | Firefox 44 stops offering RC4 | Switched off | Deprecating 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 2016 | Chrome removes RC4 Planned for a release around January or February 2016. | Switched off | TLS in Chrome Chrome will remove support for the RC4 cipher in a future release around January or February 2016. |
| 9 Aug 2016 | Edge and Internet Explorer 11 disable RC4 | Switched off | RC4 is now disabled in Microsoft Edge and Internet Explorer 11 RC4 is now disabled in Microsoft Edge and Internet Explorer 11 |
Sources
- RFC 2246, The TLS Protocol Version 1.0 IETF · Jan 1999 · checked 28 Oct 2026
- On the Security of RC4 in TLS Royal Holloway Information Security Group · 13 Mar 2013 · checked 28 Oct 2026
- SSL Pulse: now tracking forward secrecy and RC4 Qualys · 9 Oct 2013 · checked 28 Oct 2026
- RFC 7465, Prohibiting RC4 Cipher Suites IETF · Feb 2015 · checked 28 Oct 2026
- Deprecating the RC4 Cipher Mozilla · 11 Sep 2015 · checked 28 Oct 2026
- TLS in Chrome Chromium project · Sep 2015 · checked 28 Oct 2026
- RC4 is now disabled in Microsoft Edge and Internet Explorer 11 Microsoft Edge team · 9 Aug 2016 · checked 28 Oct 2026
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.
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.
| Date | Event | Kind | Source |
|---|---|---|---|
| 18 Nov 1996 | SSL 3.0 specification Published for the record as RFC 6101 in August 2011. | Standard published | RFC 6101, The Secure Sockets Layer (SSL) Protocol Version 3.0 the November 18, 1996, version of the protocol. |
| Jan 1999 | RFC 2246 (TLS 1.0) published | Standard published | RFC 2246, The TLS Protocol Version 1.0 This document specifies Version 1.0 of the Transport Layer Security (TLS) protocol. |
| Aug 2008 | RFC 5246 (TLS 1.2) published | Standard published | RFC 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 2014 | POODLE breaks SSL 3.0 | Attack published | This 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 2015 | RFC 7568 prohibits SSL 3.0 | Deprecation set | RFC 7568, Deprecating Secure Sockets Layer Version 3.0 SSLv3 MUST NOT be used. |
| Aug 2018 | RFC 8446 (TLS 1.3) published | Standard published | RFC 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 2018 | Browsers announce the end of TLS 1.0 and 1.1 Chrome | Deprecation set | Modernizing Transport Security TLS 1.0 and 1.1 will be disabled altogether in Chrome 81. |
| Mar 2020 | Safari and Firefox disable TLS 1.0 and 1.1 | Switched off | Deprecation 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 2021 | RFC 8996 deprecates TLS 1.0 and 1.1 | Deprecation set | RFC 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
- RFC 6101, The Secure Sockets Layer (SSL) Protocol Version 3.0 IETF · Aug 2011 · checked 28 Oct 2026
- RFC 2246, The TLS Protocol Version 1.0 IETF · Jan 1999 · checked 28 Oct 2026
- RFC 5246, The Transport Layer Security (TLS) Protocol Version 1.2 IETF · Aug 2008 · checked 28 Oct 2026
- This POODLE bites: exploiting the SSL 3.0 fallback Google · 14 Oct 2014 · checked 28 Oct 2026
- RFC 7568, Deprecating Secure Sockets Layer Version 3.0 IETF · Jun 2015 · checked 28 Oct 2026
- RFC 8446, The Transport Layer Security (TLS) Protocol Version 1.3 IETF · Aug 2018 · checked 28 Oct 2026
- Modernizing Transport Security Google · 15 Oct 2018 · checked 28 Oct 2026
- Deprecation of Legacy TLS 1.0 and 1.1 Versions Apple WebKit · 15 Oct 2018 · checked 28 Oct 2026
- RFC 8996, Deprecating TLS 1.0 and TLS 1.1 IETF · Mar 2021 · checked 28 Oct 2026
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.
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.
| Date | Event | Kind | Source |
|---|---|---|---|
| 18 Nov 1997 | IEEE 802.11-1997 published The standard that defines WEP. | Standard published | IEEE 802.11-1997 Published: 1997-11-18 |
| 2001 | Fluhrer | Attack published | Weaknesses 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 |
| 2006 | WPA2 required on all certified products | Standard published | Technical Note: Removal of TKIP from Wi-Fi Devices Wi-Fi Alliance has required WPA2 on all Wi-Fi CERTIFIED products since 2006. |
| 2007 | 104-bit WEP key recovered from under 40 Tews, Weinmann and Pyshkin, IACR ePrint 2007/120. | Attack published | Breaking 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 2015 | Certified devices may no longer offer TKIP-only modes | Switched off | Technical Note: Removal of TKIP from Wi-Fi Devices Effective Date: March 16, 2015 |
| Oct 2017 | KRACK key reinstallation attacks on WPA2 | Attack published | Key Reinstallation Attacks We discovered serious weaknesses in WPA2, a protocol that secures all modern protected Wi-Fi networks. |
| 25 Jun 2018 | WPA3 introduced | Standard published | Wi-Fi Alliance introduces Wi-Fi CERTIFIED WPA3 security the next generation of Wi-Fi® security |
| 2020 | WPA3 mandatory for new certified products | Deprecation set | Eight Wi-Fi trends expected in 2020 will become mandatory for all new Wi-Fi CERTIFIED™ products. |
Sources
- IEEE 802.11-1997 IEEE SA · 18 Nov 1997 · checked 28 Oct 2026
- Weaknesses in the Key Scheduling Algorithm of RC4 Fluhrer, Mantin and Shamir (copy at Cornell) · 2001 · checked 28 Oct 2026
- Technical Note: Removal of TKIP from Wi-Fi Devices Wi-Fi Alliance · 16 Mar 2015 · checked 28 Oct 2026
- Breaking 104 bit WEP in less than 60 seconds IACR ePrint 2007/120 · 2007 · checked 28 Oct 2026
- Key Reinstallation Attacks Vanhoef and Piessens, KU Leuven · Oct 2017 · checked 28 Oct 2026
- Wi-Fi Alliance introduces Wi-Fi CERTIFIED WPA3 security Wi-Fi Alliance · 25 Jun 2018 · checked 28 Oct 2026
- Eight Wi-Fi trends expected in 2020 Wi-Fi Alliance · Jan 2020 · checked 28 Oct 2026
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.
-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.
| Date | Event | Kind | Source |
|---|---|---|---|
| Apr 1998 | COMP128 broken | Attack published | A 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 1999 | A5/1 implementation published Briceno, Goldberg and Wagner; verified against official test vectors. | Attack published | A pedagogical implementation of A5/1 (code header) which has been verified against official A5/1 test vectors |
| Apr 2001 | MILENAGE example algorithm set published 3GPP TS 35.205 V3.0.0. | Standard published | 3GPP 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 2002 | A5/3 specified 3GPP TS 55.216 V1.0.0 | Standard published | SP-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 2004 | GSMA proposes withdrawing A5/2 from handsets | Deprecation set | S3-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 2009 | A5/1 rainbow tables computed by volunteers Nohl and Paget, 26C3. | Attack published | GSM: SRSLY? (26C3) Add a weak cipher trivially breakable after a few months of distributed table generation |
| 15 Jun 2015 | Singapore approves 2G closure for April 2017 | Deprecation set | MNOs to close 2G networks from 1 April 2017 (Internet Archive copy) to close their 2G networks with effect from 1 April 2017. |
| 1 Apr 2017 | Singapore 2G networks closed | Switched off | MNOs to close 2G networks from 1 April 2017 (Internet Archive copy) |
| Apr 2021 | Swisscom switches off 2G | Switched off | The 2G network is history at Swisscom in mid-April 2021 it finally switched off the 2G technology. |
| 2025 | GSMA guidance on 2G and 3G sunsets | Still in use | NG.121 2G/3G Sunset Guidelines v3.0 Mobile operators are announcing 2/3G sunset |
Sources
- A pedagogical implementation of A5/1 (code header) Briceno, Goldberg and Wagner (copy at Cryptome) · 10 May 1999 · checked 28 Oct 2026
- 3GPP TS 35.205 V3.0.0 3GPP · Apr 2001 · checked 28 Oct 2026
- SP-020506, A5/3 and GEA3 specifications 3GPP TSG SA#17 · Sep 2002 · checked 28 Oct 2026
- S3-040376, Withdrawal of A5/2 from handsets GSMA to 3GPP SA3 · May 2004 · checked 28 Oct 2026
- GSM: SRSLY? (26C3) Chaos Computer Club · Dec 2009 · checked 28 Oct 2026
- MNOs to close 2G networks from 1 April 2017 (Internet Archive copy) IDA Singapore · 15 Jun 2015 · checked 28 Oct 2026
- The 2G network is history at Swisscom Swisscom · 14 Apr 2021 · checked 28 Oct 2026
- NG.121 2G/3G Sunset Guidelines v3.0 GSMA · 2025 · checked 28 Oct 2026
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.
11 from the attack to a deprecation date.
| Date | Event | Kind | Source |
|---|---|---|---|
| 28 Dec 2007 | Crypto-1 partly reverse engineered Nohl and Plötz, 24C3. | Attack published | 24C3: Mifare |
| 7 Mar 2008 | 48-bit keys recovered from MIFARE Classic | Attack published | Security flaw in MIFARE Classic allows the (48 bit) cryptographic keys to be relatively easily retrieved. |
| 18 Jul 2008 | Court allows the attack to be published NXP's injunction request refused in Arnhem. | Attack published | Court decision on publication (press release) may publish his article on the Mifare Classic Chip. |
| Oct 2008 | Dismantling MIFARE Classic published About 200 million cards in use. | Attack published | Dismantling MIFARE Classic there are about 200 million mifare Classic tags in use around the world |
| 4 Jul 2018 | Dutch public transport decides to replace MIFARE Classic | Deprecation set | Kamerstuk 23645 nr. 670 Deze nieuwe betaaltechniek zal de huidige techniek achter de OV-chipkaart (Mifare Classic) vervangen. |
| 28 Oct 2026 | NXP still sells MIFARE Classic Page checked on this date; security-relevant applications are pointed to DESFire and Plus. | Still in use | MIFARE Classic product page |
Sources
- 24C3: Mifare Chaos Computer Club · 28 Dec 2007 · checked 28 Oct 2026
- Security flaw in MIFARE Classic Radboud University Digital Security group · 7 Mar 2008 · checked 28 Oct 2026
- Court decision on publication (press release) Radboud University · 18 Jul 2008 · checked 28 Oct 2026
- Dismantling MIFARE Classic Garcia et al., ESORICS 2008 · Oct 2008 · checked 28 Oct 2026
- Kamerstuk 23645 nr. 670 Dutch House of Representatives · 13 Sep 2018 · checked 28 Oct 2026
- MIFARE Classic product page NXP · 28 Oct 2026 · checked 28 Oct 2026
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.
-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.
| Date | Event | Kind | Source |
|---|---|---|---|
| 12 Jun 1998 | SSH-1 insertion attack on the CRC-32 check | Attack published | SSH 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 2006 | RFC 4251 to 4254 (SSH-2) published | Standard published | RFC 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 2015 | OpenSSH 7.0 disables SSH-1 and DSA keys by default | Switched off | OpenSSH 7.0 release notes Support for ssh-dss, ssh-dss-cert-* host and user keys is disabled by default at run-time. |
| 19 Dec 2016 | OpenSSH 7.4 removes the SSH-1 server | Switched off | OpenSSH 7.4 release notes This release removes server support for the SSH v.1 protocol. |
| 26 Sep 2021 | OpenSSH 8.8 disables SHA-1 RSA signatures | Switched off | OpenSSH 8.8 release notes This release disables RSA signatures using the SHA-1 hash algorithm by default. |
| 1 Jul 2024 | OpenSSH 9.8 announces DSA removal | Deprecation set | OpenSSH 9.8 release notes OpenSSH plans to remove support for the DSA signature algorithm in early 2025. |
| 9 Apr 2025 | OpenSSH 10.0 removes DSA | Switched off | OpenSSH 10.0 release notes This release removes support for the weak DSA signature algorithm |
Sources
- SSH insertion attack advisory (Internet Archive copy) CORE SDI · 12 Jun 1998 · checked 28 Oct 2026
- RFC 4251, The Secure Shell (SSH) Protocol Architecture IETF · Jan 2006 · checked 28 Oct 2026
- OpenSSH 7.0 release notes OpenSSH · 11 Aug 2015 · checked 28 Oct 2026
- OpenSSH 7.4 release notes OpenSSH · 19 Dec 2016 · checked 28 Oct 2026
- OpenSSH 8.8 release notes OpenSSH · 26 Sep 2021 · checked 28 Oct 2026
- OpenSSH 9.8 release notes OpenSSH · 1 Jul 2024 · checked 28 Oct 2026
- OpenSSH 10.0 release notes OpenSSH · 9 Apr 2025 · checked 28 Oct 2026
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.
-3 from the deprecation date to the first switch-off; still in use 17 years after the standard.
| Date | Event | Kind | Source |
|---|---|---|---|
| Mar 2005 | RFC 4033 to 4035 (DNSSEC) published | Standard published | RFC 4033, DNS Security Introduction and Requirements DNS Security Introduction and Requirements |
| 15 Jul 2010 | Root zone signed | Standard published | Root 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 2016 | Root ZSK increased to 2048 bits | Switched off | Root 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 2018 | First root KSK rollover | Switched off | KSK Rollover 2018 On 11 October 2018, ICANN performed a Root Zone Domain Name System Security Extensions (DNSSEC) KSK rollover |
| Jun 2019 | RFC 8624 marks SHA-1 signing algorithms not recommended RSASHA1 and RSASHA1-NSEC3-SHA1 stay mandatory for validation. | Deprecation set | RFC 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 2022 | SHA-1 algorithms at about 7% of their peak deployment | Still in use | DNSSEC algorithms for TLDs and everyone else these are down to approximately 7% of their peak deployment levels. |
| 11 Oct 2026 | Second root KSK rollover | Switched off | ICANN reports Root Zone KSK rollover completed as planned was completed on 11 October 2026. |
Sources
- RFC 4033, DNS Security Introduction and Requirements IETF · Mar 2005 · checked 28 Oct 2026
- Root DNSSEC status page (Internet Archive copy) ICANN and Verisign · 15 Jul 2010 · checked 28 Oct 2026
- Root zone ZSK now 2048 bits (dns-operations list) Verisign · 1 Oct 2016 · checked 28 Oct 2026
- KSK Rollover 2018 ICANN · 11 Oct 2018 · checked 28 Oct 2026
- RFC 8624, Algorithm Implementation Requirements and Usage Guidance for DNSSEC IETF · Jun 2019 · checked 28 Oct 2026
- DNSSEC algorithms for TLDs and everyone else APNIC blog · 24 Mar 2022 · checked 28 Oct 2026
- ICANN reports Root Zone KSK rollover completed as planned ICANN · 15 Oct 2026 · checked 28 Oct 2026
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.
10 from the deprecation date to the first switch-off.
| Date | Event | Kind | Source |
|---|---|---|---|
| Jul 2005 | RFC 4120 (Kerberos V5) published | Standard published | RFC 4120, The Kerberos Network Authentication Service (V5) This document provides an overview and specification of Version 5 of the Kerberos protocol |
| 2008 | AES in Windows Kerberos Windows Vista and Windows Server 2008. | Standard published | Kerberos Enhancements (Windows Vista and Windows Server 2008) enables the use of AES 128 and AES 256 encryption with the Kerberos authentication protocol. |
| Jul 2012 | RFC 6649 deprecates DES in Kerberos | Deprecation set | RFC 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 2018 | RFC 8429 deprecates RC4 and triple DES in Kerberos | Deprecation set | RFC 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 2022 | Windows makes AES the default session key type KB5021131. | Switched off | KB5021131: 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. |
| 2024 | Windows Server 2025 domain controllers stop issuing RC4 ticket-granting tickets | Switched off | Detect and remediate RC4 usage in Kerberos Starting with Windows Server 2025, domain controllers don't issue RC4 Ticket Granting Tickets. |
| 14 Apr 2026 | Domain controllers stop assuming RC4 by default Phased from January to July 2026. | Switched off | How 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 |
Sources
- RFC 4120, The Kerberos Network Authentication Service (V5) IETF · Jul 2005 · checked 28 Oct 2026
- Kerberos Enhancements (Windows Vista and Windows Server 2008) Microsoft · 2008 · checked 28 Oct 2026
- RFC 6649, Deprecate DES, RC4-HMAC-EXP, and Other Weak Cryptographic Algorithms in Kerberos IETF · Jul 2012 · checked 28 Oct 2026
- RFC 8429, Deprecate Triple-DES (3DES) and RC4 in Kerberos IETF · Oct 2018 · checked 28 Oct 2026
- KB5021131: How to manage the Kerberos protocol changes related to CVE-2022-37966 Microsoft · 8 Nov 2022 · checked 28 Oct 2026
- Detect and remediate RC4 usage in Kerberos Microsoft · 2024 · checked 28 Oct 2026
- How to manage Kerberos KDC usage of RC4 for service account ticket issuance (CVE-2026-20833) Microsoft · 14 Apr 2026 · checked 28 Oct 2026
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.
6 from the deprecation date to the first switch-off.
| Date | Event | Kind | Source |
|---|---|---|---|
| Nov 1998 | RFC 2409 (IKEv1) published | Standard published | RFC 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 2005 | RFC 4306 (IKEv2) published | Standard published | RFC 4306, Internet Key Exchange (IKEv2) Protocol This document describes version 2 of the Internet Key Exchange (IKE) protocol. |
| Oct 2014 | RFC 7296 (IKEv2) becomes the Internet Standard | Standard published | RFC 7296, Internet Key Exchange Protocol Version 2 (IKEv2) This document obsoletes RFC 5996, and includes all of the errata for it |
| Sep 2017 | RFC 8247 bars DES from IKEv2 Triple DES downgraded to MAY. | Deprecation set | RFC 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 2017 | RFC 8221 sets triple DES to SHOULD NOT in ESP | Deprecation set | RFC 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 2023 | RFC 9395 moves IKEv1 to Historic | Switched off | RFC 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. |
Sources
- RFC 2409, The Internet Key Exchange (IKE) IETF · Nov 1998 · checked 28 Oct 2026
- RFC 4306, Internet Key Exchange (IKEv2) Protocol IETF · Dec 2005 · checked 28 Oct 2026
- RFC 7296, Internet Key Exchange Protocol Version 2 (IKEv2) IETF · Oct 2014 · checked 28 Oct 2026
- RFC 8247, Algorithm Implementation Requirements and Usage Guidance for IKEv2 IETF · Sep 2017 · checked 28 Oct 2026
- RFC 8221, Cryptographic Algorithm Implementation Requirements and Usage Guidance for ESP and AH IETF · Oct 2017 · checked 28 Oct 2026
- RFC 9395, Deprecation of the Internet Key Exchange Version 1 (IKEv1) Protocol and Obsoleted Algorithms IETF · Apr 2023 · checked 28 Oct 2026
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.
| Date | Event | Kind | Source |
|---|---|---|---|
| 2005 | Suite B announced | Standard published | Fact 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 2015 | NSA announces a transition to quantum-resistant algorithms | Deprecation set | Suite 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 2022 | CNSA 2.0 published Transition for national security systems complete by 2035. | Deprecation set | Announcing 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. |
Sources
- Fact Sheet NSA Suite B Cryptography (Internet Archive copy, 2005) NSA · 2005 · checked 28 Oct 2026
- Suite B Cryptography page as revised August 2015 (Internet Archive copy) NSA · 19 Aug 2015 · checked 28 Oct 2026
- Announcing the Commercial National Security Algorithm Suite 2.0 NSA · 7 Sep 2022 · checked 28 Oct 2026