4 ms·
Why DNS over HTTPS? Not sure if i'm missing something, but i don't consider privacy protection slopware.
by rapatel0 2mo ago
Why DNS over HTTPS?
Not sure if i'm missing something, but i don't consider privacy protection slopware.
- cullumsmith 2mo agoI run a local DNS server that has its own blocklists, internal DNS records, etc. I imagine most people who might bother to deploy an enterprise browser policy do something similar.
- thesuitonym 2mo agoUnless you're running your own local DoH server, it's just privacy theater, and not even good theater. It's the same bogus argument made in favor of retail VPNs. "Encrypt your traffic so your ISP can't spy on you!" Meanwhile failing to recognize that you're just moving the spying agency to some free service owned by--oh, let's look at the top providers... Cloudflare (not great), Brave (advertising company), Google (Bad)... Need I go on? Perhaps you've forgotten that old adage: if you're not the customer, you're the product.
- sandcat_ 2mo agoSecurity theatre is far too strong. It’s not perfect but it does solve real world, actively exploited privacy flaws, such as ISPs monitoring and selling insights from DNS, NXDOMAIN hijacking, etc. Your internet traffic is all MITMd by Cloudflare anyway. Using their DNS barely moves the needle.