How to keep your ISP’s nose out of your browser history with encrypted DNS

Re:How to keep your ISP’s nose out of your browser history w... by jakobdabo on Sunday April 08, 2018 @05:29PM (#16788531)

Getting rid of plaintext SNI won't help much.

The domain is there in the certificate itself. There are, of course, some (or maybe many, I don't have statistics) certificates for multiple domains (wildcard and alt. name), but still.

[ Parent | on HN ]

Re:How to keep your ISP’s nose out of your browser history w... by cesarb on Sunday April 08, 2018 @05:33PM (#16788552)

> The domain is there in the certificate itself.

With TLS 1.3, the certificate is in the encrypted portion of the handshake.

[ Parent | on HN ]

Re:How to keep your ISP’s nose out of your browser history w... by dingaling on Monday April 09, 2018 @05:57AM (#16791660)

However as I understand the protocol the very first step of the TLS 1.3 handshake, the nonce generation, can be MiTMed sufficiently to allow an attacker to determine the target domain. It's only in the next step that server and client do authentication.

The attacker can't trivially continue the handshake beyond that point but that might give enough info to log the attempt and terminate the connection.

[ Parent | on HN ]

Re:How to keep your ISP’s nose out of your browser history w... by MertsA on Monday April 09, 2018 @07:53AM (#16792168)

Or just connect up a second connection and see what certificate they send back.

[ Parent | on HN ]

Re:How to keep your ISP’s nose out of your browser history w... by jakobdabo on Sunday April 08, 2018 @05:44PM (#16788626)

That's nice to hear. I stand corrected, thank you.

[ Parent | on HN ]