5 ms·
We already know they do - they’ve injected ads + “suggestions” instead of dns failures in the past. They’ve also injected permanently unique cookies in http re
by olliej 7y ago
We already know they do - they’ve injected ads + “suggestions” instead of dns failures in the past.
They’ve also injected permanently unique cookies in http requests.
ISPs can’t be trusted as dumb pipes, they’re closer to “clueless criminal” pipes.
But I agree with you, I don’t particularly trust google either.
- tptacek 7y agoGoogle's design doesn't ask you to trust Google more than you already do if you use Chrome. It doesn't default you to Google's DNS servers, will honor your current nameservers, and will upgrade you to DoH at any of those servers who support it. I'm honestly not sure what more you could ask for from Google on this particular issue.
- judge2020 7y agoThe UI bug tracker is private so we don't know if there might also be a "select DNS resolver" option and/or a checkbox for "encrypt DNS" in Settings.
- colordrops 7y ago> Google's design doesn't ask you to trust Google more than you already do if you use Chrome. So in other words trust them with everything.
- LaGrange 7y ago> Google's design doesn't ask you to trust Google more than you already do if you use Chrome. ...well, I don't, so there. Also, this is true if I'd _only_ use Chrome, and never used other software for networking. Damn, I actually used to respect you. This is so disappointing.
- damq 7y agoA whole bunch of irrelevant retorts + a personal attack. I've never seen a comment more deserving of getting flagged than this one.
- olliej 7y agoI also don’t use chrome :p Google has promoted its own DNS service over others in the past, including for non-chrome users, and presumably would do the same when DoH (in whatever form) is the norm. I was simply saying we already know that ISPs misbehave, but presuming that Google wouldn’t is not necessarily a clear cut decision.
- rgbrenner 7y agoYes, Google used the right approach here. They honor your DNS settings, and upgrade it if it's available. Firefox, on the other hand, plans to force all of their users to trust Cloudflare by default.. and most users won't even know they made that change.
- gruez 7y ago[deleted]
- nuclear_eclipse 7y agoThe article itself says this.
- bsimpson 7y agoThe article?
- GeekyBear 7y ago>Firefox, on the other hand, plans to force all of their users to trust Cloudflare by default.. and most users won't even know they made that change. Mozilla has explicitly stated on their blog that they don't intend to make any change to a user's DNS settings without getting the user's consent. >When DoH is enabled, users will be notified and given the opportunity to opt out 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...
- judge2020 7y agoThis is something I really think should be opt-in, even if it's via a notification toast.
- topranks 7y agoThe problem is it’s just a banner with “ok” at the top, which clearly says “we’ve increased your privacy by (insert technical jumbo jumbo here).” As Bert Hubert pointed out, to most users it ends up looking like this: https://twitter.com/powerdns_bert/status/1123666707279695874?s=21 https://twitter.com/powerdns_bert/status/1123666707279695874...
- daedalus_j 7y agoSo it's more like HSTS for DNS? Auto-switch to encryption if our chosen target supports encryption? Because that seems MUCH more sensible than a lot of the stories/comments about this recently make it seem.
- tptacek 7y agoNo. The HSTS security model is per-site; the DoH model covers all sites. If you get DoH working anywhere, it's working for you everywhere.
- topranks 7y agoYes, as Google plan you implement it, which is fine. Most of the hulaboo is about Mozilla who are moving customers DNS queries to Cloudflare en mass, regardless of what DNS server they have already configured.
- nickodell 7y agoThat's true, but Google has made no commitment to keep it that way.
- undersuit 7y agoI still have something like 15 Spectrum Bogus NXDomains blacklisted on OpenWRT. When I set it up the page they were redirecting too was still the Charter page with a half done Find/Replace of Charter/Spectrum.