4 ms·
https://support.mozilla.org/en-US/kb/configuring-networks-disable-dns-over-https https://support.mozilla.org/en-US/kb/configuring-networks-di...
by swinglock 7y ago
https://support.mozilla.org/en-US/kb/configuring-networks-disable-dns-over-https https://support.mozilla.org/en-US/kb/configuring-networks-di...
- phs318u 7y agoOuch! Thanks for the reality check. If I consider the trade-off with respect to where the majority of threats are likely to come from for most users, I can understand why Mozilla have made this choice. Nevertheless there should have been some kind of user announcement (perhaps when the feature first went live), to inform the users of this critical feature, which has the potential to significantly change their security posture (for good or ill depends on where your threats are coming from, which depends on you).
- swinglock 7y agoIf those checks don't determine enabling the feature would impact the user experience or security, they do supposedly announce and ask whether it should be enabled, otherwise it's kept disabled. At least for "the US rollout", which I assume is currently the only rollout rather than only US users being asked. I don't quite see what's "ouch" about that, although personally I won't enable it. https://support.mozilla.org/en-US/kb/firefox-dns-over-https https://support.mozilla.org/en-US/kb/firefox-dns-over-https