5 ms·

How about enabling DNS-over-HTTPS, which routes your entire browsing history to a third party, based on selections labelled "OK, Got It" and "Disable Protection

by dpifke 7y ago

How about enabling DNS-over-HTTPS, which routes your entire browsing history to a third party, based on selections labelled "OK, Got It" and "Disable Protection": https://github.com/mozilla/doh-rollout/issues/125 https://github.com/mozilla/doh-rollout/issues/125 Don't get me wrong, DoH is great if you have a shady ISP. But it should be opt-in, not opt-out, since those of us who don't have shady ISPs don't want all our DNS queries centralized in the same place, to be scooped up with just one FISA warrant. And dark patterns like this are a pox on the web and Mozilla shouldn't be perpetuating them.

deleted 7y ago
[deleted]
dangerface 7y ago
> since those of us who don't have shady ISPs don't want all our DNS queries centralized If you live in the US or EU your ISP logs dns queries and sells them on [0] encryption is the only solution. [0] https://www.ispreview.co.uk/index.php/2019/04/big-uk-broadband-isps-have-big-concerns-about-dns-over-https.html https://www.ispreview.co.uk/index.php/2019/04/big-uk-broadba...
cptskippy 7y ago
Your complaint is about a Web Extension Experiment that they're currently testing and not a feature they have shipped in the browser. It seems like this isn't shady at all, but rather they're testing something and soliciting feedback. You provided some and they responded that they plan to write a blog post about it. So what's shady here? That the process is working?
- dpifke 7y ago
  My understanding is that this is how it's being rolled out, eventually to 100% of users: https://blog.mozilla.org/futurereleases/2019/09/06/whats-next-in-making-dns-over-https-the-default/ https://blog.mozilla.org/futurereleases/2019/09/06/whats-nex...
  - farisjarrah 7y ago
    I still don't think its shady. Mozilla have publicly stated that its possible to change the DOH provider, and furthermore they have clearly laid out their requirements for Cloudflare to participate in this experiment. This seems like a good compromise in order to force other providers to start encrypting dns requests.
magashna 7y ago
For their release in the US it's assumed that your ISP is shady.
shadowgovt 7y ago
"OK, Got It" and "Disable Protection" is pretty accurate. It's inconvenient, but it turns out the "open, anonymous" web has huge trust issues that bad actors use to exploit and attack the unknowing. Some of that is most readily solved by nudging users to trusted third-parties. You can have issue with whether that third party should be trusted, but the larger issue is that the user has to trust some third party for DNS to work at all, and most don't even think twice about that question. > since those of us who don't have shady ISPs don't want all our DNS queries centralized If you don't hae a shady ISP, disable protection. You're already protected by your ISP not being shady, right? ;) The average user has no idea if they should trust their ISP's DNS.

by dpifke 7y ago

deleted 7y ago

[deleted]

dangerface 7y ago

> since those of us who don't have shady ISPs don't want all our DNS queries centralized If you live in the US or EU your ISP logs dns queries and sells them on [0] encryption is the only solution. [0] https://www.ispreview.co.uk/index.php/2019/04/big-uk-broadband-isps-have-big-concerns-about-dns-over-https.html https://www.ispreview.co.uk/index.php/2019/04/big-uk-broadba...

cptskippy 7y ago

Your complaint is about a Web Extension Experiment that they're currently testing and not a feature they have shipped in the browser. It seems like this isn't shady at all, but rather they're testing something and soliciting feedback. You provided some and they responded that they plan to write a blog post about it. So what's shady here? That the process is working?

dpifke 7y ago
My understanding is that this is how it's being rolled out, eventually to 100% of users: https://blog.mozilla.org/futurereleases/2019/09/06/whats-next-in-making-dns-over-https-the-default/ https://blog.mozilla.org/futurereleases/2019/09/06/whats-nex...
- farisjarrah 7y ago
  I still don't think its shady. Mozilla have publicly stated that its possible to change the DOH provider, and furthermore they have clearly laid out their requirements for Cloudflare to participate in this experiment. This seems like a good compromise in order to force other providers to start encrypting dns requests.

magashna 7y ago

For their release in the US it's assumed that your ISP is shady.

shadowgovt 7y ago

"OK, Got It" and "Disable Protection" is pretty accurate. It's inconvenient, but it turns out the "open, anonymous" web has huge trust issues that bad actors use to exploit and attack the unknowing. Some of that is most readily solved by nudging users to trusted third-parties. You can have issue with whether that third party should be trusted, but the larger issue is that the user has to trust some third party for DNS to work at all, and most don't even think twice about that question. > since those of us who don't have shady ISPs don't want all our DNS queries centralized If you don't hae a shady ISP, disable protection. You're already protected by your ISP not being shady, right? ;) The average user has no idea if they should trust their ISP's DNS.