Live data from Hacker News

Firefox’s Trusted Recursive Resolver DNS feature is dangerous

blog.ungleich.ch

171–180 of 306 posts

Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous

#171
If you don't trust local ISPs the solution is not to put your eggs into the cloudflare basket which could then be plundered by the NSA fox.

Instead tunnel all traffic to some rented box in a jurisdiction of your choice and then run your own DNS resolver either in your home network or on that box.

Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous

#172
post #26

Sigh. Mozilla had just made Firefox usable again... And now good reasons for leaving it again are coming up.

You can disable it...

But for the majority of users, it's probably good to have Mozilla negotiate favorable terms with a DNS provider that can be subject to audits, etc.

Who audits your ISP? Does Mozilla do that?

Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous

#173
post #143

Sorry if this is off topic but where does DNS over https leave my pi hole? Is it possible (in the future) to do dns over https from my router to the pihole and then dns over https from the pihole to Google or Cisco open DNS? How would it work? Wouldn’t the router need to trust the https certificate that my pihole presents? Thank you!

That would work. DoH is "just" a replacement for UDP in this context. However when Mozilla changes the default to DoH of Cloudflare, you will need to manually change all firefox installations.

Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous

#174
post #68
post #59

That s just a feature. You can choose not to use it. Why so much noise?

As I understand it that's even the default choice, and CloudFlare is just the provider they're currently testing this with for those who do choose and do not configure their own provider.

The point is though that users won't change their defaults. When Mozilla sets the default to Cloudflare, > 99.9% of the users will use it.

Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous

#176
post #164

Earlier quoted context omitted.

The 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,…

So.. in some future Mozilla might select a default DNS provider on your behalf. Did you consider the upside? Mozilla can negotiate on your behalf. Mozilla can obtain favorable terms of service, concessions in privacy, third-party reviews. Things you would never be able to negotiate for. If you think of Mozilla as negotiating on your behalf, they have motive to protect you, and they have the leverage to get concession…

It’s already happening: the DoH endpoint that Mozilla defaults to on the CF-Side has a stronger privacy agreement as per https://blog.nightly.mozilla.org/2018/06/01/improving-dns-pr...

Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous

#177
> The Domain Name System (DNS) is a service used in converting a computer’s host name or a Top-Level Domain (TLD) into an IP address

Hostnames and TLDs are different concepts in DNS. It is a mistake to conflate them.

TLDs are the top level (rightmost) part of domain names, such as specifically “com” in “example.com”.

Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous

#179

Earlier quoted context omitted.

The 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.

The 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.

TFA is wrong.

Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous

#180

This proposal introduces a lot of complexity. It requires JSON parsing, HTTP and TLS. A bug in one of these components could is likely to occur. In contrast, DNS is very simple and can be implemented with a lot less code.

The JSON/HTTP protocol may be more complex than DNS, but Firefox is likely to already have a very good implementation. TLS is new, but important.
Post reply on HN