Why TLS 1.3 isn't in browsers yet
Dec 26, 2017Nick Sullivan
Summary
This post details the challenges and technical reasons behind the delayed adoption of TLS 1.3 in major browsers. It explains the historical context of TLS version negotiation, the impact of the POODLE vulnerability and insecure downgrade attacks, and how these issues led to middlebox ossification and incompatibility with TLS 1.3's design. The post highlights the need for correct implementation of version negotiation and the role of middleboxes in hindering protocol upgrades.
More from the Website Security & Threat Management trail
- We tested our own WAF with frontier AI models. Here’s what we found
- When scanners miss the attack: how Cloudflare Client-Side Security protects storefronts
- Introducing automatic remediation policies with Cloudflare CASB
- Introducing context-aware vulnerability discovery and remediation with Cloudflare Managed Defense and OpenAI Daybreak Models
- Introducing Adaptive Intelligence: undermining the economics of every bot attack