Thank you for raising this issue; I had forgotten about it. I agree
that it's an extremely severe problem.
One possible solution would be to enable DNS-over-HTTPS, which I believe
is supported by IceCat-68 although it's disabled by default. See:
https://support.mozilla.org/en-US/kb/firefox-dns-over-https
I see.
Incidentally, I think that a case can be made that enabling this is a
sensible default for most users, even when not using Tor, because it
prevents the user's ISP from snooping on and hijacking DNS lookups.
Whereas most users have little or no choice about their ISP, we can
choose a default DNS-over-HTTPS provider that commits to a strong
privacy policy. Also, the provider is user-configurable. However,
I acknowledge that any such decision would be controversial.
I second this. It should be enabled by default, as IceCat is distribution of FireFox with Freedom, Security and Privacy.
This can be made like an add-on just like HTTPS-Everywhere and LibreJS, where a user can easily on or off the feature.
I agree that it would be much better to remove it outright than to
provide a broken Tor Button that doesn't actually work. However, if we
can fix it, I think that we should.
I am still not sure whether the issue is with Tor Button or the browser itself.
Tor Button just automatically modifies proxy values of the network settings of browser.
If the dns traffic is not routed via tor, even after the change in proxy settings,
then the issue must be with the browser itself, right?
Regards,
RG.
signature.asc