TLS 1.3 Adoption

Discussions center on challenges of upgrading to TLS 1.3 from TLS 1.2, including compatibility issues, middlebox interference, deprecation of older versions, and comparisons of features and performance.

➡️ Stable 0.6x Security

4,436

Comments

Years Active

Top Authors

#9941

Topic ID

Activity Over Time

2008

2009

2010

2011

2012

2013

246

2014

367

2015

346

2016

368

2017

359

2018

456

2019

329

2020

350

2021

371

2022

312

2023

253

2024

227

2025

295

2026

Top Contributors

tptacek (194) tialaramex (159) yuhong (58) toast0 (49) hannob (31)

Keywords

GCM CPU hosts.rb NI X1 L107 JVM DTLS ETS cloudflare.com tls aes client server extension versions version 128 clients deprecated

Sample Comments

DyslexicAtheist • Oct 19, 2016 • View on HN

no I was talking TLS 1.2https://www.ietf.org/mail-archive/web/tls/current/msg21278.h...

cpach • Apr 12, 2022 • View on HN

What features does if offer that we can’t do today with TLS?

jeroenhd • Mar 3, 2020 • View on HN

Why limit yourself to TLS 1.2? What's wrong with TLS 1.3?

Thorrez • Aug 29, 2024 • View on HN

Reminds me of the TLS 1.3 upgrade and GREASE.https://blog.cloudflare.com/why-tls-1-3-isnt-in-browsers-yet...

collsni • Dec 7, 2019 • View on HN

Tls sadly won't make a difference.

zephius • Apr 15, 2025 • View on HN

Yeah, just like TLS 1.2 support. Don't even get me started on how that fiasco is still going.

feld • Dec 9, 2014 • View on HN

TLS 1.3 isn't finished yet...

sargun • Apr 26, 2024 • View on HN

Far less due to TLS being ubiquitous

andersen1488 • Apr 5, 2016 • View on HN

What exactly is wrong with TLS? Why the switch?

fredgrott • Feb 14, 2021 • View on HN

more than that as they have to use old tls libs no longer maintained and no longer receive security patches ouch!