16 ms·
DNS over HTTPS is a great idea. There's nothing wrong with the protocol or Mozilla's implementation of it. This article is all about Mozilla's default choice fo
by jillesvangurp 8y ago
DNS over HTTPS is a great idea. There's nothing wrong with the protocol or Mozilla's implementation of it. This article is all about Mozilla's default choice for a DNS provider. I think Cloudflare is actually a reasonable choice though I'm not a big fan of their annoying captchas that I get served whenever I use vpns.
There's nothing sneaky going on here; which the article seems to imply.
Currently there is no UI to configure any of this yet (other than about:config) but you can trivially select any DNS provider that implements this in the same place where you turn this on. The relevant setting is network.trr.uri. Also, you need to opt in to this to turn it on so you'd be reviewing this setting as well. Also you can configure how this is used, how and when it falls back to normal DNS, etc.
You can run your own server if you want; or use the one from your provider if/when they implement this. For obvious reasons, there are not a lot of usable servers yet but it seems Google has implemented this as well. So I assume they plan to roll this out for Chrome at some point.
The premise of this article seems to be that you should trust your provider to do DNS and do it well. I'm sorry to say but for the vast majority of providers I have experience with the opposite is the case. I've had providers redirect dns failures to advertising pages in the past, shitty performance (600 ms or worse), and generally trying to rip me off with bad network infrastructure related outages while charging me a premium for bandwidth clearly not delivered via obviously very congested infrastructure. I have no reason whatsoever to trust them, at all. The less they can learn from my traffic the better.
- dingo_bat 8y agoI have configured my network settings to use a particular set of DNS servers. The issue is Firefox going out of the way to use something else.
- wild_preference 8y agoHorrible seems like a pretty melodramatic word here compared to your explanation.
- oxymoron 8y agoThe feature is opt-in. Firefox will use your system configured DNS servers unless you explicitly enable DOH. In that case you can still change Cloudfare for some other server if you’d like.
- dingo_bat 8y agoThe impression I got from TFA is that the feature will be on by default and you have to dig into about:config to disable it.
- Xylakant 8y agoTFA is wrong.
- kiriakasis 8y agoThey retracted it
- nebulous1 8y agoThe article doesn't suggest there's something sneaky going on. The article is suggesting that Mozilla are choosing to share your DNS queries with a third party service by default, which is exactly what they're doing. It's not about them choosing Cloudflare in particular, it's about them choosing any particular service by default. And the article's argument that, if you have to choose somebody to share this data with, it might as well be the people you already share it with, seems pretty valid to me. edit: I have to point out that the article has backed away from the claim that this will be enabled by default in September. Looking at the Mozilla blog, they mention wanting to enable this by default but have no actual plan to do so (and more crucially doesn't discuss at all what sort of form it would have to be in for them to enable it by default, it may look nothing like the cloudflare-default we're discussing here).
- Xylakant 8y agoThe default applies currently if you enable an experimental feature. They hammered out a tight privacy agreement for one service and use that as default while this is stabilized. You can pick any other resolver if you prefer. Seems a legit way of handling this. > And the article's argument that, if you have to choose somebody to share this data with, it might as well be the people you already share it with, seems pretty valid to me. The whole point of HTTPS and DNS-over-HTTPS is to not share any data at all with your provider. It’s not entirely working right now due to SNI being plaintext, but work is being done on that, too. So that’s really not a good argument.
- nebulous1 8y ago> The whole point of HTTPS and DNS-over-HTTPS is to not share any data at all with your provider. It’s not entirely working right now due to SNI being plaintext, but work is being done on that, too. So that’s really not a good argument. If that was the whole point of https then we wouldn't have plaintext SNI. I can't even begin to understand why you think that there being a draft of an SNI encryption standard makes it 'really not a good argument'.
- 8y ago
- ahnick 8y agoAccording to the article this is enabled by default to use Cloudflare. Are you saying that is not the case?
- Xylakant 8y agoThe article provides no source for this assertion and this Mozilla blog post is pretty clear that DNS-over-HTTPS is off by default and defaults to CF if you enable it or are part of the shield study (which requires nightly and opt-in to shield studies in the first place) https://blog.nightly.mozilla.org/2018/06/01/improving-dns-privacy-in-firefox/ https://blog.nightly.mozilla.org/2018/06/01/improving-dns-pr...
- ahnick 8y agoIf this is true, then I'm okay with the feature being available if it is opt-in. Although I generally think this is a concern better left outside of the particular browser I'm using. If I want to route DNS queries through a third party then I'd like to do that for all my network traffic, not just my browser.
- pard68 8y agoI agree. I use DNSCrypt and route my requests through a different server each time. That said, Joe User doesn't know how to setup any DNS server. Even going into Window's Control Panel gets Joe User anxious. Joe User doesn't care enough about privacy to learn how to set it up system wide. And for Joe User this would cover 99% of his internet usage.
- lol768 8y ago>DNS over HTTPS is a great idea Why is it better than DNS over TLS? All I can see here is increased overhead.
- oxymoron 8y agoHarder to distinguish between DNS queries and other traffic. Since a lot of censorship is DNS based that’s significant.
- kiriakasis 8y agoThis is really the main point. I support this but it has its downsides, for example flixbus blocks YouTube on their free WiFi. I think they have all the rights to do it as some site are heavier to support than others and they might be forced to shut it off if it became common (Also a lot of people don't have earphones on them an being beside someone watching "funny" YouTube videos at 3am is torture (end of personal rant...))
- yjftsjthsd-h 8y agoWouldn't this be better served by bandwidth limiting/shaping?
- kiriakasis 8y agothat would mean that if many people used youtube they would all have terrible speed, which would make their wifi look of bad quality. The primary purpose of their on board wifi is to buy tickets and check connections. In this case video streaming might really be more expensive than necessary
- yjftsjthsd-h 8y agoI mean limiting per-user bandwidth. So if you try to watch youtube on your personal 1Mb slice, good luck, but you won't drag down anyone else, and for the stated goals of buying tickets and such it's fine.
- pmlnr 8y ago> DNS over HTTPS is a great idea Putting everything, even lower-than-http level things on top of HTTP is a horrible idea, introducing yet another layer of abstraction.
- kevingadd 8y agoIt's important to understand the advantages of HTTPS via other protocols or custom crypto: * HTTPS stacks are battle tested and there are multiple of them. Browsers in particular already ship a heavily maintained one that performs great, so using DNS on top of it gets all those benefits. Because there are multiple stacks the risk of people settling on a monoculture is a lot lower. * People running a DNS resolver likely have the ability to run a good HTTPS server already, including having certs ready to go. Likewise, there are a bunch of battle tested httpd implementations out there and good https stacks to go with them. * Proxies, reverse proxies, caching, etc are all well understood for HTTPS * HTTPS2 has transport compression all figured out, so if you turn that on (which is 'free' once your server+client both support it) you're getting compression for free. HTTPS2 also supports multiple channels so if one request is pending you can still kick off another one over the same socket. * Any debugging tools you can use with HTTPS can be used with DNS. It's possible for a raw DNS protocol, or DNS+TLS, to pick up all of these benefits but DNS-over-HTTPS gets them almost entirely for free. fwiw, web proxies over HTTPS2 are great too. The performance is great even over long distances because of the multiple channels and compression features.
- pmlnr 8y agoIs there anything left, that's not on HTTP? Maybe NTP. I know about JMAP to replace IMAP. Here's another idea: other protocols are useful as well, sometimes more useful, than HTTP. > HTTPS stacks are battle tested and there are multiple of them. So is DNS. I wonder how the HTTP servers deal with DNS amplification attacks. > People running a DNS resolver likely have the ability to run a good HTTPS server already Your conclusion lacks any indication of evidence. > Because there are multiple stacks the risk of people settling on a monoculture is a lot lower. HTTP _is_ becoming a monoculture. Sort of. I know it's an open standard, and everything, but still.
- RaleyField 8y ago> There's nothing sneaky going on here; It bloody is. Egregiously so. If they are deviating from expected behaviour[1] they should obtain informed consent and even then it's unethical. Half of Mozilla is screaming decentralisation[2], the other is centralising the web as fast as they can. I still haven't forgiven Linux Mint for similar shenanigans[3]. [1] Users understand instinctively the principle behind reverse dns lookup. If ISPs can resolve at least portion of domain names then it doesn't make sense to then introduce another completely random third party that isn't strictly necessary for the process. [2] https://hacks.mozilla.org/2018/07/introducing-the-d-web/ https://hacks.mozilla.org/2018/07/introducing-the-d-web/ [3] https://bugs.launchpad.net/linuxmint/+bug/1133777 https://bugs.launchpad.net/linuxmint/+bug/1133777
- wvh 8y agoDNS over HTTPS might or might not be a great idea; but I'm critical whether centralised is better than the current decentralised approach. You're putting all your eggs in one basket, which might become an exceedingly interesting target.
- jiveturkey 8y ago> I have no reason whatsoever to trust [any ISP], at all. You also have no reason to trust cloudflare, at all.