IANA 0x11ECRather than an automated blog feed, we maintain a curated, human-verified log updated only when NIST, the IETF TLS Working Group, NSA CNSA 2.0, or major TLS/SSH implementations change something engineers need to act on.
OpenSSL 3.5 added built-in FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), and FIPS 205 (SLH-DSA) algorithms plus hybrid X25519MLKEM768 TLS 1.3 group negotiation without requiring external out-of-tree plugins.
Primary source: OpenSSL Project Release Notes
NIST published Initial Public Draft IR 8547 establishing a concrete 2030 deprecation milestone and 2035 full disallowance milestone for RSA-2048, ECDSA, EdDSA, and classical finite-field/elliptic-curve Diffie-Hellman.
Primary source: NIST IR 8547 IPD
OpenSSH 9.9 introduced NIST FIPS 203 ML-KEM-768 combined with X25519 as its default post-quantum hybrid SSH key-exchange algorithm ahead of sntrup761x25519-sha512.
Primary source: OpenSSH 9.9 Release Notes
NIST published the final versions of its first three post-quantum standards and instructed implementers to transition away from pre-standard Kyber and Dilithium draft codepoints.
Primary source: NIST FIPS 203 Final
Filter verified post-quantum TLS 1.3 engineering guides and dated standards advisories across NIST FIPS 203-205, OpenSSL 3.5+, OpenSSH 9.9+, and CycloneDX v1.6 CBOM workflows.
Automated upstream standards watcher polls IETF TLS WG, OpenSSL, and OpenSSH release feeds every 48 hours; human editor verifies all configuration guidance before promotion.
Run a browser-equivalent wire ClientHello offering X25519MLKEM768 (0x11EC) and calculate Harvest-Now-Decrypt-Later overlap.
Compare encapsulation key sizes, ciphertext byte budgets, and security categories for standardised post-quantum primitives.
Copy tested production configuration blocks and multi-packet ClientHello middlebox diagnostic probes.
Sequence external TLS ingress upgrades, east-west service meshes, PKCS#11 HSM firmware validation, and root CA transitions.
Generate machine-readable cryptoProperties inventories across certificates, TLS listeners, and code repositories.
Wire-level TLS 1.3 ServerHello verification across reference developer and standards origins shows hybrid X25519MLKEM768 (0x11EC, 1,120-byte server share) active on CDN-fronted endpoints while several major code hosts remain on classical 32-byte X25519.
Actionable takeaway: Test both CDN edge hostnames and direct origin load balancers separately; CDN edge termination does not automatically protect origin-to-origin mTLS.
OpenSSL 4.1.0 is a feature release adding significant new functionality to OpenSSL. This release incorporates the following potentially significant or incompatible changes: Added VC-WIN32-MSVC2013 and VC-WIN64A-MSVC2013 build targets to...
Actionable takeaway: Review OpenSSL changelog notes for TLS 1.3 ML-KEM / ML-DSA provider updates across ingress containers.
OpenSSL 3.5 integrated native FIPS 203, FIPS 204, and FIPS 205 implementations and enabled hybrid X25519MLKEM768 negotiation directly in libssl group configuration lists.
Actionable takeaway: Prioritise OpenSSL 3.5+ base images in container and reverse-proxy build pipelines to retire legacy oqs-provider forks.
NIST Initial Public Draft IR 8547 set a concrete 2030 deprecation milestone and 2035 disallowance milestone for quantum-vulnerable RSA, ECDSA, EdDSA, and classical ECDH.
Actionable takeaway: Align multi-year PKI root rotation and hardware HSM procurement cycles to complete classical deprecation ahead of 2030.
OpenSSH 9.9 promoted FIPS 203 ML-KEM-768 paired with X25519 ahead of Streamlined NTRU Prime for administrative SSH transport.
Actionable takeaway: Pin KexAlgorithms mlkem768x25519-sha256 in /etc/ssh/sshd_config across bastion and jump hosts.
Reviewed by Callum Reid, Principal Infrastructure & Cryptography Editor
Tracks NIST CSRC publications and IETF TLS Working Group specifications.
Last reviewed:
Updated when primary standards or implementations ship
AI-assistance & editorial check: Research outlining and formatting are assisted by AI tools in an offline draft workflow. Nothing on this site publishes automatically without verification. A named human editor opens and verifies every primary source link, command snippet, and factual statement prior to publication. See our Editorial Policy and Corrections Policy.
Store your email for low-noise standards updates once dispatches begin. No emails are sent yet.