CloudflareSuleman AhmadAnnouncement
Automatic Key Exchange: faster, post-quantum secure origin handshakes for 45 billion daily connections (and counting)
Summary
Cloudflare’s Automatic Key Exchange addresses extra TLS 1.3 handshake latency and the difficulty of enabling post-quantum origin connections without manual configuration. Cloudflare previously sent an X25519 keyshare as its first guess; origins preferring another group returned a HelloRetryRequest, while sending X25519MLKEM768 indiscriminately risked oversized, split ClientHello messages and legacy compatibility failures. The system reuses Automatic SSL/TLS scanning to run lightweight handshakes for each supported group, map every origin’s capabilities and preferences, and tailor the initial keyshare, preferring X25519MLKEM768 when supported. During rollout, HelloRetryRequests dropped from roughly 52% to 3.7%, cutting more than 150 ms from p90 handshake latency, while hundreds of thousands of domains gained post-quantum origin connections without configuration. Cloudflare says it plans to extend scanning to post-quantum authentication, including ML-DSA certificates and future Merkle Tree Certificates.
Context
TLS 1.3 requires the client to select a key agreement algorithm in its first packet. A wrong choice causes a HelloRetryRequest and an additional round trip; manually enabling post-quantum origin connections could also risk compatibility problems. Cloudflare describes automatic configuration as necessary to expand protection against harvest-now, decrypt-later attacks without requiring website operators to become cryptography experts.
Approach / What changed
Automatic Key Exchange reuses the Automatic SSL/TLS scanning pipeline to perform lightweight TLS handshakes offering individual key agreement groups, including X25519, P-256, P-384, P-521, and X25519MLKEM768. Cloudflare uses the measured capabilities and preferences of each origin to select its initial keyshare, preferring the post-quantum hybrid when supported while avoiding configurations that could disrupt connections.
Takeaways
HelloRetryRequests fell from roughly 52% to 3.7% during rollout, reducing p90 connection handshake latency by more than 150 ms.
X25519MLKEM768 keyshares are 1,216 bytes versus 32 bytes for X25519, which can split ClientHello messages across packets and expose compatibility issues with legacy middleboxes or origin servers.
The share of origins supporting post-quantum key agreement rose from 0.5% in 2023 to 12.8%, while hundreds of thousands of domains received post-quantum origin connections without manual setup.
Source and freshness
- Source
- blog.cloudflare.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.