As a man in a country where constant censoring is performed by the government this movement at least make it harder for the gov censor/monitor people.
Firefox’s Trusted Recursive Resolver DNS feature is dangerous
41–50 of 306 posts
Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous
#42> My local ISP seems more trustworthy to me than a big US-based corporate which acts under the guise of a selfless privacy rights defender. I have never trusted any local ISP. They’re commonly expressly allowed by law to share roughly whatever they like about you†, and they are known to do so . Cloudflare has at least promised not to be evil, and is to be audited annually concerning it. If they desire to be evil I ha…
I wonder what kind of ISPs you use? Here in .ch, ISPs can be rather small and you even know the operators personally. So trust ISP >> cloudflare.
I’ve also spent time in India with a small ISP, and I hated their DNS: they actively intercepted all DNS and replaced it with their own OpenDNS arrangement, involving the horrible NXDOMAIN replacement that was still a thing at the time, and in such a way that you couldn’t opt out of it! I don’t know how trustworthy they might or might not have been (I didn’t personally know them), but I do know that I loathed their technical decisions and would fain have bypassed them.
Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous
#43Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous
#44For them this sounds like a good deal (is money involved here?). Having more control of DNS should mean they can provide better service for their customers.
Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous
#45Earlier quoted context omitted.
Your home router will. However, as the article made clear, you won't be able to open that site in Firefox. Even if you were, you won't be able to get a public TLS certificate for that site, making you unable to serve the site as HTTPS and locking you out of many current and all(!) futue JS and CSS features. Yes, you can solve both problems by installing overrides. However, this has to be done separately for every cli…
That's my point. My parent said that private DNS names have been dead for a while, and I said they aren't.
Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous
#46Earlier quoted context omitted.
I wonder what kind of ISPs you use? Here in .ch, ISPs can be rather small and you even know the operators personally. So trust ISP >> cloudflare.
I live in Australia; ISPs are basically all big entities, altogether unworthy of trust. The US is broadly similar. In both countries, you do get some obscure tiny ISPs, but they’re fairly rare overall. I’ve also spent time in India with a small ISP, and I hated their DNS: they actively intercepted all DNS and replaced it with their own OpenDNS arrangement, involving the horrible NXDOMAIN replacement that was still a…
Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous
#47Nothing against Cloudflare, but I don’t think it is good in general for the Internet that they are getting so critical. For them this sounds like a good deal (is money involved here?). Having more control of DNS should mean they can provide better service for their customers.
Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous
#48More information: https://blog.nightly.mozilla.org/2018/06/01/improving-dns-pr... According to this page: - you can already test this right now - you can provide your own server And some more: https://en.wikipedia.org/wiki/DNS_over_HTTPS
Nobody will do this except for maybe 5 individuals and a few dozen cooperations simply because there are no other public DoH servers around.
Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous
#49This feature will break dns-based geo-lookup, so as a user I might get directed to services that are 130ms away from me instead of 1-5ms. For any client application, this will likely have strong negative effects on user experience.
Re: Firefox’s Trusted Recursive Resolver DNS feature is dangerous
#50Sigh. Mozilla had just made Firefox usable again... And now good reasons for leaving it again are coming up.