2 ms·
This is/ will be part of the dividend from TLS 1.3 encrypting more of the handshake. Historically deploying a feature like delegated credentials was impractica
by tialaramex 7y ago
This is/ will be part of the dividend from TLS 1.3 encrypting more of the handshake.
Historically deploying a feature like delegated credentials was impractical because some large and unpredictable fraction of connections would go like this:
Popular Web Browser: "Hi, I want to talk TLS 1.2 to somesite.example, I know how to handle DelegatedCredentials if you've got any"
Some Site: "Hi, here's our delegated credentials for somesite.example and now let's..."
"Security" MITM Box: "Oh no you don't scumbag! I don't recognise that certificate - FIN. FIN. This connection is an attack!"
With TLS 1.3 that MITM box's operator has to make a decision up front, since it can't understand the part where the remote server actually identifies itself because that's now encrypted. It can either just give up and let the Popular Web Browser do TLS 1.3 unmolested and not break random features OR it can proxy everything and then since it doesn't claim to understand DelegatedCredentials the remote server won't bother trying to use them.
This way if you have middle boxes everything stays no worse than before, but if you don't you get the benefit of new features.
Unfortunately although TLS 1.3 makes it possible to begin deploying this, the end game which reaps the benefits seems a bit fraught. But hey, can't get there if you don't start.