Having just read https://ungleich.ch/en-us/cms/blog/2019/09/11/turn-off-doh-firefox/ I think that if Fedora means it seriously to treat its audience as Friends, it would be indeed in its best intention to follow the OpenBSD's lead[*] and disable said technology by force till there's time (till it's not enabled en masse). Not to speak of concerns related to GDPR (saying as an EU citizen). Interested users could still opt in if they wish so. Such a change, relying on principles the internet used to work upon since it's dawn and gradually evolved (DNSSEC), could hardly be viewed as intrusive. How to do that in terms of about:config settings is described in said article. Thanks for consideration. [*] https://twitter.com/phessler/status/1171358689342697473
Also consider the whole-distro perspective, please. A particular program should not circumvent system-wide policy, especially when a slight confidentiality is at stake as mentioned. Relying solely on libc currently enforces this system-wide policy. In the actuality for the past few years, the distro works in exactly the opposite direction, see https://fedoraproject.org/wiki/Changes/CryptoPolicy and follow-ups during the subsequent Fedora releases. Firefox would just throw a wrench into these well meant efforts to make the overall (security sensitive) behaviour unified and hence effectively comprehensible by the system administrator. This aspect needs to be taken account as well. It may come the time the distro policy will be to have a local DNS resolver capable of DoH by default, with reasonable opt-in end-points in the offer. The technology as such is not evil. Pushing that unconditionally down the throat of the users of an isolated program ... well, can be.
Yes, we're going to disable DoH by default for Fedora / RHEL.
Added to firefox-69.0-10, may be released in upcoming 69.0.1 update.
Great to hear this, indeed, thanks for taking it seriously!
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.