search

mozilla-mobile / fenix

⚠️ Fenix (Firefox for Android) moved to a new repository. It is now developed and maintained as part of: https://github.com/mozilla-mobile/firefox-android
https://github.com/mozilla-mobile/firefox-android
Mozilla Public License 2.0
6.47k stars 1.27k forks source link

Bring back DNS over HTTPS to Firefox Android for privacy #14261

Closed pathbreak closed 4 years ago

pathbreak commented 4 years ago

What is the user problem or growth opportunity you want to see solved?

Until versions < 79.0.5, Firefox for Android supported DNS-over-HTTPS for better privacy. In 79.0.5, this feature has been removed. All DNS requests from Firefox go out unencrypted via ISPs in older Android versions which don't support device-wide DNS settings. This has actually reduced privacy of Firefox (although the PR announcements for this release claim the opposite). Although I have filed this as a feature request, I feel this is actually a regression bug.

How do you know that this problem exists today? Why is this important?

DNS over HTTPS improves privacy. See this article by Mozilla.

Who will benefit from it?

DNS over HTTPS improves privacy for all. See this article by Mozilla. For users living in internet censoring regimes, it's a simple user-friendly solution to access blocked websites and has helped improve adoption of Firefox.

┆Issue is synchronized with this Jira Task

kbrosnan commented 4 years ago

Duplicate #4584

andrew-aitchison commented 4 years ago

This is not a duplicate of #4584 - that bug was about adding a user interface. This bug is a regression in Android v80; before that tDNS-over-HTTPS functionality was available via about:config, but that feature has been removed, so there is no way to enable DNS-over-HTTPS in v80.

For what is is worth, the UK ISP TalkTalk has a parental controls option KidSafe which blocks DNS requests to *.mozilla.org. Thus this bug means I cannot access mozilla sites from Android unless I open up the entire internet to my children ...

cadeyrn commented 4 years ago

This is not a duplicate of #4584 - that bug was about adding a user interface. This bug is a regression in Android v80; before that tDNS-over-HTTPS functionality was available via about:config, but that > feature has been removed, so there is no way to enable DNS-over-HTTPS in v80.

So, in fact, it is a duplicate of #4584.

andrew-aitchison commented 4 years ago

??? Sorry I don't see a feature request as a plausible duplicate of a regression bug. If https://github.com/mozilla-mobile/fenix/issues/4584 can be marked as a regression, I would find that a suitable response.

Otherwise, your reply is pretty much using up what little goodwill I have left for Mozilla, after the disappearence of about:config and https://twitter.com/EmilyKager/status/1289308930972278789

I chose to use the previous Firefox for Android on my phone and tablet. I cannot use the new Firefox for Android to do the things I used to do (like submit bug-reports to mozilla :-) and I will switch to another browser when I can find a less unsatisfactory alternative.

Oh, and your suggestion https://github.com/mozilla-mobile/fenix/issues/7865#issuecomment-679351305_ of adding options for every useful feature previously in about:config sounds like causing a lot of code and binary bloat. Many tweaks that power-users enjoy justify an about:config option but writing a gui interface seems like overkill. If that is no longer what firefox is about, it is no longer the browser I have used and loved since it took over from the original Mozilla browser.

cadeyrn commented 4 years ago

???

I don't understand your question.

It's a feature request for the simple reason that it's not a bug but a not implemented feature. But to be honest: It doesn't matter if you call it a feature request or a regression because it doesn't change the fact that you want to configure DoH and that #4584 is exactly about this. So it's a duplicate. Either of #4584 or of #7865 if you want to use about:config for that. It's that easy.

Oh, and your suggestion #7865 (comment)_ of adding options for every useful feature previously in about:config sounds like causing a lot of code and binary bloat

No. I didn't suggested to add options for everything. I suggested to the user to open a feature request a) because it was the only reason why he wanted to use about:config and b) because the user said it's a "pretty valid use case for a common user" and that's a strong argument for an option - if it's really true (telemetry and user research can probably tell more). But I can't see how my comment in response to another user in an unrelated issue should be relevant for your feature request.