25 ms·
Improving DNS Privacy in Firefox
- Vinnl 8y agoRelated: A cartoon intro to DNS over HTTPS. https://hacks.mozilla.org/2018/05/a-cartoon-intro-to-dns-over-https/ https://hacks.mozilla.org/2018/05/a-cartoon-intro-to-dns-ove...
- jwilk 8y agoOn HN: https://news.ycombinator.com/item?id=17196415 https://news.ycombinator.com/item?id=17196415
- Seipaho8 8y ago> While sophisticated users can turn to cloud-based “open resolvers” Sophisticated users run their own resolvers instead of relying on unverifiable promises from for-profit entities.
- kyledrake 8y agoThis doesn't solve the problem. Those resolvers are also unencrypted.
- zamadatix 8y agoAnd how do these sophisticated users populate their own revolvers if not plain DNS, DNS over TLS, or DNS over HTTPS? There is no such thing as hosting a globally distributed database from your house.
- Seipaho8 8y agoThe point is that they are not a single central entity easily siphoned off by an org that'll sell the information for profit.
- gnode 8y agoThere seems to be little point of doing this, in my opinion, when SNI doesn't secure the hostname.
- zzzcpan 8y agoAgreed, SNI and DNS need to be fixed together, not separately. And definitely without centralized services, like Cloudflare. Otherwise why not just go all the way with centralization and provide secure proxy for everyone in the browser.
- phicoh 8y agoThey are completely independent protocols, with their own issues in this area. For the DNS, the specification for DNS over TLS is almost trivial. DNS over HTTPS is a bit more tricky because their are more possibilities, interactions with HTTPS, etc. But still not very hard from a protocol point of view. Operationally, DNS over TLS/HTTPS is mostly unknown. So it will take quite a bit of time before it is well know how to actually run that as a service at scale. Encrypting the SNI in TLS is mostly the other way around. Fixing that has significant impact on the protocol. There is no point in making very complex changes in TLS, which is already a tricky protocol without the DNS community committing to provide DNS over TLS/HTTPS at scale. At the same time, securing traffic between a DNS stub resolver and the recursive resolver prevents are lot of middle box issues (but also creates a completely new set of issues). So it is worth deploying the even if TLS still leaks the SNI.
- zzzcpan 8y agoThey cannot be independent if actual privacy is concerned. At least sharing a threat model that touches both layers.
- phicoh 8y agoThey are mostly independent. Your privacy loss is by and large the sum (or max) of the privacy loss caused by DNS and TLS individually. For TLS, the threat model is relatively simple: only an on path attacker has access to a plaintext SNI. In the context of route hijacks, 'on path' is not as simple as it sounds, but route hijacks are relatively rare. For DNS the situation is much more complex. You have to consider not only traffic between stub resolver and recursive resolver, but also between recursive resolver and the various auth. resolvers. At the end of the day, you need to consider all places where information is leaked and whether you want to do something about that or not. And in that sense DNS is independent from TLS.
- userbinator 8y agoBecause there is no encryption, other devices along the way might collect (or even block or change) this data too. ...which is sometimes very desirable[1][2][3]. I get the whole "more security!" movement, but also feel like it's just contributing to turning general-purpose computers into locked-down media consumption devices. [1] https://pi-hole.net/ https://pi-hole.net/ [2] https://en.wikipedia.org/wiki/Proxomitron https://en.wikipedia.org/wiki/Proxomitron [3] https://news.ycombinator.com/item?id=17196888 https://news.ycombinator.com/item?id=17196888
- lima 8y agoImportant for intrusion detection in locked-down enterprise environments, too. But you can still inspect TLS handshakes, it's just a lot more work...
- st3fan 8y agoI don't think you 'get' the "whole "more security!" movement" at all actually :-)
- icebraining 8y agoNone of that is affected as long as the browser lets you explicitly choose to use them, as Firefox does.
- arghwhat 8y ago#1 and #2 are not hindered by "more security". They're local proxies you set up and decide to trust. In a proper setup, you would use encrypted communication towards that proxy, and that proxy would use encrypted communication towards the appropriate server, maintaining privacy and authentication while implementing their purpose. Both of them are a bit of a hack, though, as this really belongs in the client application. More generally, more security does not stop any legitimate use-cases. You just chose to extend your trust. #3 doesn't have anything to do with the subject at hand. Network interception is never something a user wants, and does not implement additional security. It's common in enterprise and banking environments for all the wrong reasons (enough that these industries were trying to harm TLS1.3 when they realized that the increased security was troublesome). Such a setup is by no means necessary, and due to there being Bad People in this world, the ability to do so is dangerous. Repressive governments that wish to control or manipulate information is a very good example, and sacrificing silly enterprise politics is a very small price to pay to help the repressed. The result of There are quite a few places where this is the case, even though it might be hard to imagine for someone in the west (despite filtering occurring in the west too, whenever the government dislikes a site).
- rajadigopula 8y agoDNSCrypt is also a viable option. - https://dnscrypt.info/ https://dnscrypt.info/
- jedisct1 8y agodnscrypt-proxy also supports DNS-over-HTTPS and is probably the most popular DoH client. You can use it to connect to Cloudflare or other DoH servers, and this will not be limited to queries sent by Firefox. On iOS, use DNSCloak.
- rajadigopula 8y agoAdGuard app on android also allows dnscrypt to route all the phone communications go through the dns crypt servers encrypted without rooting.
- zamadatix 8y ago"On the Firefox network and security teams, we’re working to change that by encrypting DNS queries and by testing a service that keeps DNS providers from collecting and sharing your browsing history." Adding an authentication header prevents alteration but it does not present a viable option to the problem statement.
- nbsd4life 8y agoso, there's a concurrent post about how 1.1.1.1 had an outage. Does that mean web browsing won't work if that happens again? If not, does that mean it will fallback to unencrypted DNS if 1.1.1.1 is blocked? Making this a default means that Firefox users all bypass censorship in several countries, what do they expect to happen as a result of it? Firefox blocked? 1.1.1.1 blocked?
- arghwhat 8y agoThis isn't any different from if your normal DNS server is blocked, and 1.1.1.1 is not the only encrypted DNS provider. If whatever DNS you use doesn't work, then you cannot resolve any new domain names until you change to another DNS server or it gets fixed. Recently used domains will be cached in will thus still work.
- AlphaWeaver 8y agoThe post also notes that they won't be using the 1.1.1.1 address, though they'll be using Cloudflare. They'll likely be using another address which is less likely to be blocked.
- Operyl 8y agoMost likely because 1.1.1.1 still doesn't work on networks like AT&T.
- OptionX 8y agoCould people in heavly-restricted regions, like China and such, access blocked sites if they use DoH to DNS outside the control of the censoring entity?
- majewsky 8y agoThe censoring entity can still block the IPs of the services, but it's an additional difficulty (unless they're willing to block e.g. all of Cloudfront when someone hosts their website on S3).
- zzzcpan 8y agoThey can't block something like domain fronting themselves, have to "ask" companies that host them to help. But they can easily block resolvers by IP, SNI, etc, if not already.
- sanxiyn 8y agoSouth Korean government censors DNS of North Korean websites. (I think this is stupid and South Korean government should stop immediately.) I tested Firefox DoH implementation and it does circumvent South Korean censorship.
- Tharkun 8y agoWhy would I want my browser to do this? My browser should use the DNS configured by my OS -- in my case, a local, caching resolving NS. If I want to use some kind of DNS-over-HTTP I'll tell my OS to do it. I don't want my browser making DNS decisions for me. What am I missing?
- Proven 8y agoYou’re missing the BS PR - Mozilla is trying to “stay relevant”. While they harvest and aggregate user data. Your actual privacy is of secondary concern.
- cerberusss 8y agoBecause at the moment, no major OS supports it.
- j605 8y agodnscrypt-proxy (https://github.com/jedisct1/dnscrypt-proxy https://github.com/jedisct1/dnscrypt-proxy) supports all major platforms and checkout https://dnscrypt.info https://dnscrypt.info for more options.
- nly 8y agoIt's worth noting that this is from the principle developer of libsodium as well.
- dao- 8y agoYou're missing that you can still configure the browser to your needs? You seem to be a power user so you can do this. Mozilla cares about average users too, and doesn't have control over OS defaults that may not be optimal for average users' privacy.
- andrewaylett 8y agoI, too, have a local caching resolver. And I'm unlikely to turn this on at the browser level, although I'm occasionally tempted to play with it in the resolver. But I strongly suspect we're in the minority and that something like this is the easiest -- and quite possibly the only -- way for many users to avoid DNS poisoning by ISPs.
- josteink 8y agoCore internet protocols like DNS over HTTP? Yet another step closer to HTTP/IP, I guess. Can’t say I condone it.
- kyledrake 8y agoI think the main reason this happens is because SSL is a pain to configure and develop and it's easier to just use HTTP's SSL than to make an SSL version of everything else. It wouldn't be my first choice for a lot of reasons, but HTTP2 is getting pretty close to just being a binary protocol anyways.
- sanxiyn 8y agoDNS over TLS is RFC 7858. It already exists.
- sanxiyn 8y agoThere is also DNS over TLS. DNS over HTTPS is basically DNS over TLS, but with workaround for port blocking.
- Lennie 8y agoWith eventually a plan to allow for HTTP-caching, use of CDNs, pushing updates over HTTP/2 push, running it over QUIC, etc.
- zamadatix 8y agoYou can't condone it because you'd prefer "DNS over TLS" or a you have a notion that DNS shouldn't have other headers before it because it's a core protocol and should reimplement the functionality it needs frome TLS? In the case of the former I agree, the browser should be doing this over TLS as HTTP isn't giving any additional protocol functionality. In the case of the latter the purpose of protocol encapsulation isn't that the most important comes first it's that you can abstract service layers instead of remaking them for each new thing.
- avian 8y agoI don't see how this improves privacy. Yes, my local ISP, whose DNS I'm using, knows the domains I'm connecting with. They most likely can also access this info in cleartext in other ways, if they care enough. For instance through SNI. Beyond my ISP, it's doubtful that unencrypted nature of DNS has any impact on my privacy due to heavy caching and the fact that my requests are merged together with requests from many other users. With DNS over HTTP a single third-party overseas now gets access to this list of domains I'm connecting with. It all just seems like a thinly veiled attempt at more centralization of internet services. Yes, my residential ISP and my coffee shop, library, etc. don't have these "very strong privacy agreements". But I think it's less likely they will all combine their logs to track my behavior than a single centralized entity.
- bzbarsky 8y agoThere are plans to remove the SNI privacy leak as well. Note that "your local ISP" means "whatever coffeeshop you are using wifi in", for laptop users, right? You're right that if the resolver decides to keep and correlate logs that's bad. It's pretty key to use a resolver that you trust to not do that...
- zackbloom 8y agoYour ISP is very likely literally selling your DNS data to the highest bidder right now. They don't not have a strong privacy agreement out of laziness, they don't have one because your traffic data is valuable.
- KaiserPro 8y agoNo, no no and no. It does not improve privacy, it just puts all your DNS history in the hands of one provider. Not only that it adds latency for no real gain. HTTP is a terrible protocol for anything time sensitive. (its a fairly bad protocol for anything fast or efficient full stop.) The better way to do this is encourage/provide DNSsec (so we know that a provider is who they say they are) and then encrypt dns queries between servers. Firstly that stops everything being centralised by default, (kinda, DNSSec has a chain of trust, so thats centralised) DNS is a massively scalable fault tolerant, distributed key value store. Far faster and more reliable than toys like Etcd and the like. secondly you don't then loose geolocation/provider steering for nearest/fastest node. (yes you can get meta data from IP, but that's not really that useful, that means the _service_ has to figure out how to route your request, not the upstream DNS.) But it needs improvements to make its more anonymous, slapping a fast SSL like tunnel on a resolver combined with DNSsec seems like a much better way to do this and dns over HTTP.
- sanxiyn 8y agoDNS over TLS exists as well. DNS over HTTPS is just another format for DNS over TLS.
- gnode 8y agoIn my opinion we don't want TLS at all, but rather a UDP based protocol, so that the latency advantages of DNS aren't lost. I believe DNSCurve solves this.
- sanxiyn 8y agoIf you want UDP, DNS over DTLS also exists.
- gnode 8y agoDoesn't really save you anything; DTLS still involves a connection with a handshake, so you have increased latency and memory overhead. Its usefulness is in low latency transport where head-of-line blocking would be detrimental (e.g. real-time streaming video; phone calls; VPNs). DNSCurve, by comparison, is connection-less -- meaning no handshake latency, no connection overhead, and denial-of-service resilience.
- mike-cardwell 8y agoImagine if this became the default with only Cloudflare as a provider. Firefox users in countries all over the World will not be able to visit a website locally or anywhere else without asking an American corporation for the IP address first. I mean. I can't believe that there are going to be a lot of alternative providers. It's going to be an expensive service to provide. Especially when one of the requirements is that you can't mine the data to recuperate costs (and rightly so).
- lossolo 8y agoI hope they are not making this a default setting. What about GeoDNS load balancing/routing that a lot of companies are using? Some time ago I've tested Google DNS servers and got worse location from Akamai than using my ISP DNS servers. It was before Google introduced EDNS Client Subnet (rfc7871)[1] so I don't know how things are now but probably biggest CDN providers like Akamai now give exactly the same results as you would use your own ISP DNS servers. I don't know if smaller companies/CDN providers implement it tough. How cloudflare is solving this with their 1.1.1.1 DNS server? Because if they don't then it can be really problematic for some percentage of users. [1] https://tools.ietf.org/html/rfc7871 https://tools.ietf.org/html/rfc7871
- zackbloom 8y agoIt's a balancing act between protecting the privacy of the requesting user and trying to provide enough location information that legacy services know how to route their traffic. We (Cloudflare) will likely begin providing an approximation of the ECS information which tries to strike the right balance.
- myf01d 8y agoWhile this is much better imo than just sending over DNS protocol as eliminates old DNS attacks like spoofing, it won't make users _practically_ any safer since all subsequent TCP requests have the resolved IP in the IP packet. But like I said, it's still better than the default protocol.
- peterwwillis 8y agoThe New Cabal of the Web: 1) CloudFlare, 2) Google, 3) Mozilla, 4) Let's Encrypt, 5) a smattering of contributing vendors, 6) internet-related standards bodies, and a few other orgs I'm forgetting or not familiar with. Pretty much the entire WWW is being shaped and controlled by this group. "Open Web" my ass. The really insane thing to me is that a lot of this tech is being pushed with the argument that they need to get around "port blocking". Uh. These groups setting these new standards run the most critical parts of the WWW, which is the most critical part of the Internet outside of the routing of it. They could get everyone to open up a god damn firewall port if they wanted. I mean this is just ridiculous. There's 65,535 ports and we only get to use one of them (443) because people are too lazy to do anything else?
- pitaj 8y agoYou forgot the media publishers and the government. The DMCA had and has a huge effect on the web.
- peterwwillis 8y agoYes, but not on the architecture/design of it.
- BTeam 8y agoThat's forgetting the push for EME as a W3C standard.
- beokop 8y agoThis is the world we live in. Why can’t I access websites over ipv6 even though they’re hosted on cloud providers with ipv6 support? Because just getting people to change their configuration without an immediate benefit to themselves is arguably the hardest problem for the Internet right now.
- gcp 8y agoPretty much the entire WWW is being shaped and controlled by this group. "Open Web" my ass. In reality, "they" couldn't even ship Array.prototype.flatten because a few sites won't update MooTools. What you describe couldn't be further removed from reality. https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/8R9-KS3aVls/0jhMp-RBCQAJ https://groups.google.com/a/chromium.org/forum/#!msg/blink-d...
- peterwwillis 8y agoI'm not sure how it's supposed to work through captive portals. I guess if you can't get to the DNS-over-HTTPS page, use the system resolver? But then networks will just block the DNS-over-HTTPS page implicitly to force the system resolver when they need it. Another thing this will break: corporate intranet sites. Suddenly you can't browse to your intranet site because Mozilla never checked the DNS server that your computer was assigned by the company.
- sp332 8y agoYes, you can just block cloudflare-dns.com and this will stop working. As the article mentions, Firefox will fall back to normal DNS unless you set a hard-fail flag. [Edit: firefox says they're using a different endpoint, but I'm assuming you can just block that too.] Corporate intranets are used to configuring user desktops already. This is just another switch to flip.
- jonnytran 8y agoI don't understand why everyone is so down on this. I see this as a big win for average non-techie computer users in terms of privacy. Unlike many of us here, they're not going to take the time to set up a resolver or even click a checkbox hidden in preferences. Someone needs to take the first step in making encrypted DNS on _by default_. Once more people use it, other organizations that are in a more ideal position will follow and improve on it.
- Bromskloss 8y agoWait, aren't DNS lookups done by the operating system?