2 ms·

So... the attack on this would be to take over the local nameserver (or even just system DNS resolution) of the clients trying to get to a domain and then serve

So... the attack on this would be to take over the local nameserver (or even just system DNS resolution) of the clients trying to get to a domain and then serve your own public key?

progval 6y ago
Mozilla also pushes for DNS over HTTPS, so the browser uses a hardcoded server by default (eg. Cloudflare).
justin_oaks 6y ago
That would work right up to the point where the server returns a certificate that the client needs to validate. If you're an attacker then you'd also need to have a certificate with a matching domain and is signed by a trusted certificate authority. Otherwise the client will see the certificate as untrusted. Having a trusted certificate for a domain you don't own is already the "Game Over" scenario for current TLS connections since DNS hijacking is generally much easier.
shawnz 6y ago
If you can do that, there's no need to change any keys. You can just look at the DNS requests that come in and the hostnames will be revealed that way. That is why it is important to also use encrypted DNS in addition to ESNI.