Hacker News
points by akerl_ 2 days ago | 0 comments
A reminder that the average consumer device doesn't actually validate DNSSEC in its default configuration: it relies on its recursive resolver to set a bit on the response saying "I validated DNSSEC, things are all good". In that configuration, DNSSEC gets you no protection against this.

One of the reasons a variety of providers have been pushing for DoH is because DoH fully closes the risk of ISP MITM without needing individual site operators to do anything. This is why you're seeing folks like Firefox and Chrome enable DoH by default.

[–] cowlevel 2 days ago
DoH is fine if a bit complicated. The problem is who the DoH provider is. Usually it's Cloudflare.
[–] account42 1 day ago
> One of the reasons a variety of providers have been pushing for DoH is because DoH fully closes the risk of ISP MITM without needing individual site operators to do anything.

... by replacing it with Google/Cloudflare MITM with whom the user doesn't even have a business relationship or even shared jurisdiction.

[–] akerl_ 1 day ago
The business relationship most home users have with their ISP explicitly permits that ISP to harvest data from their DNS requests.
[–] account42 1 day ago
I'm glad you know everyones ISP terms of services as well as the local laws that restrict which parts of them are worth a damn.
[–] akerl_ 1 day ago
Do you actually disagree with my claim, or is your concern purely that you don’t like my generalization?