Re:DNS-over-HTTPS Policy Requirements for Resolvers
by zzzcpan on Wednesday April 10, 2019 @10:02AM
(#19624691)
Your ISP doesn't really need DNS traffic to know things about you, IP addresses alone leak a lot of information, add to that SNI, response sizes, active probing, clear text traffic, etc. and you should realize that the only thing DoH does is letting one extra party to know what you are doing in addition to your ISP. DoH is net negative for privacy. You need at least a VPN to get to net positive, so that your ISP can't get that much data.
[ Parent
| on HN ]
Re:DNS-over-HTTPS Policy Requirements for Resolvers
by wbl on Wednesday April 10, 2019 @10:05AM
(#19624729)
How is DoH a net negative? ESNI is coming soon. Also ISPs do all sorts of other badness with DNS like NXDOMAIN interception.
Re:DNS-over-HTTPS Policy Requirements for Resolvers
by zzzcpan on Wednesday April 10, 2019 @10:08AM
(#19624762)
If you can't trust your ISP, leaking all of your DNS traffic to another party still doesn't let you trust your ISP, but now you have to trust that other party too, hence net negative. To avoid trusting your ISP you need at least a VPN.
Re:DNS-over-HTTPS Policy Requirements for Resolvers
by judge2020 on Wednesday April 10, 2019 @11:06AM
(#19625409)
ISPs already don't have a good track record, so I would argue them NXDOMAIN advertising (like Spectrum does by redirecting you to a yahoo search page) won't make someone unsubscribe from their services. But if a service like 1^4, that specifically states they don't track you, lies about it, then that would be a huge issue for all of the customers that pay for the company's other products.
Re:DNS-over-HTTPS Policy Requirements for Resolvers
by wbl on Wednesday April 10, 2019 @01:49PM
(#19627093)
Now that I use another revolver the NXDOMAIN problem is fixed.
Re:DNS-over-HTTPS Policy Requirements for Resolvers
by sroussey on Wednesday April 10, 2019 @10:22AM
(#19624902)
SNI is getting encrypted soon too
Re:DNS-over-HTTPS Policy Requirements for Resolvers
by zzzcpan on Wednesday April 10, 2019 @10:26AM
(#19624948)
Within next 10 years maybe. It doesn't solve anything though and is plenty of time for DPI vendors to pursue other snooping techniques.
Re:DNS-over-HTTPS Policy Requirements for Resolvers
by the8472 on Wednesday April 10, 2019 @12:57PM
(#19626583)
Only if you go through big, centralized cloud providers fronting the traffic. You're just replacing your ISP with the the CDN.
Re:DNS-over-HTTPS Policy Requirements for Resolvers
by Spivak on Wednesday April 10, 2019 @04:08PM
(#19628310)
The person who wrote your application stood it up using that CDN though. There are two parties we're concerned about: you and the entity you're communicating with.
You trust your device and the entity, and the entity trusts the infrastructure and services they're using. Everything else is the enemy. So moving the barrier to a CDN which the entity trusts is actually an improvement over intermediate ISPs which neither of you trust.
Re:DNS-over-HTTPS Policy Requirements for Resolvers
by the8472 on Wednesday April 10, 2019 @04:12PM
(#19628339)
They may simply not care and only "trust" the CDN in so far as it bypasses local resolvers. I.e. they might be using it for reasons not aligned with my interests and not vet the CDN at all.