I wonder if there's any proposals/extensions for moving SNI into the encrypted part of the communication. The initial certificate would have to be keyed to the IP address of the server, or maybe something from DNS, and probably there are other complications too, but it'd at least reduce the amount of plaintext information transmitted with each connection.
Comments
I wonder if there's any proposals/extensions for moving SNI into the encrypted part of the communication. The initial certificate would have to be keyed to the IP address of the server, or maybe something from DNS, and probably there are other complications too, but it'd at least reduce the amount of plaintext information transmitted with each connection.
This has been discussed ad nauseum on the TLS-WG mailing list. Just search for "encrypted SNI". Or click here for ekr's initial email: https://www.ietf.org/mail-archive/web/tls/current/msg18633.h....
Moving SNI into the encrypted channel would require completely redesigning TLS's key negotiation mechanism.
The server wouldn't know which key to use to decrypt the rest of the message.
That's called host header :-)
For HTTP, yes. There are thousands of other protocols that rely on TLS though.
Are there any other protocols that rely on SNI? Genuinely curious.
hah, i was wondering the same :)