3 ms·
So, to summarize, one of the remaining issues on the Web is that when you browse to an HTTPS site the name of the site you are connecting to is still in clearte
by kingcharles 5y ago
So, to summarize, one of the remaining issues on the Web is that when you browse to an HTTPS site the name of the site you are connecting to is still in cleartext. The reason for this is that you regularly have 1 IP address with multiple Web sites on it. The server needs to know which Web site to forward your request to. Once it has forwarded your request the SSL cert of that site takes over and all future requests are encrypted.
Encrypted Client Hello would install a server-wide certificate that would encrypt the data from the first connection so that the handshake wouldn't be visible to the outside.
The best a MITM could do is determine that you are connecting to a specific IP but would not be able to determine which site on that IP you are browsing.
- infotogivenm 5y agoDNS is still a thing but there are at least decent widely deployed solutions.
- tkot 5y agoAnd the two most popular ways to encrypt DNS queries rely on TLS (DNS over TLS and DNS over HTTPS).
- kingcharles 5y agoEncrypted DNS just resolves a name to an IP. My browser still has to connect to the IP of the web server.