3 ms·
Adam's post about agility is a good read, but it's worth remembering that it makes a prediction which did not in fact come true. > When we try to add a fourth
by tialaramex 6y ago
Adam's post about agility is a good read, but it's worth remembering that it makes a prediction which did not in fact come true.
> When we try to add a fourth (TLS 1.3) in the next year, we'll have to add back the workaround, no doubt.
Adam is talking about the unsafe downgrade fallback, traditionally done by web browsers, not so long ago even falling back to SSLv3 which was long obsolete.
But in fact today, if your web browser connects to a remote server proposing TLS 1.3 and the remote server just silently drops the connection because it can't conceive of such a thing, the browser goes "Huh, I guess TLS doesn't work on that server" not "Let's try again with TLS 1.2" because the design in TLS 1.3 actually works, even if getting there was a heroic effort. A compliant TLS 1.2 server will do TLS 1.2, and sufficiently non-compliant ones just break and are now presumably very rare.