DNS over HTTPS has _nothing_ to do with consumer privacy. The reality is, forcing DNS queries up to a 3rd party that _really_ wants your DNS data. This is like using VPNs for privacy, it doesn't give you privacy, it just moves the goalposts somewhere else.
-
Show this thread
-
Replying to @nuintari
You're confusing DoH with Mozilla's plan for DoH. You can use DoH to talk to any server that supports it, and it does reduce the exposure of your queries. That can be your own resolver, Cloudflare's, Google's, your ISP's, etc. Mozilla's deployment plan is batshit crazy tho.
1 reply 0 retweets 8 likes -
Compare with Chromium's plan for example: https://www.chromium.org/developers/dns-over-https … "our deployment model is designed to preserve the current user experience, i.e. auto-upgrading to the current DNS provider's DoH server which offers the same features" No change in who handles your DNS queries.
1 reply 0 retweets 2 likes -
What's the point then? I don't think almost anyone's thread model is "I trust my ISP but someone's sniffing the packets on their network"
1 reply 0 retweets 0 likes
1. No more stealthy DNS MITM, it has to be done with the user's permission 2. Encrypted DNS + encrypted SNI -> less privacy leakage when connecting to shared hosts (most cloud providers, Cloudflare, etc.) If you were designing DNS today, would you deliberately make it insecure?
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.