Consider enforcing HTTPS by default in Tor Browser
Hostile exit nodes can perform ssl strip attacks to steal passwords or other sensitive data. See for example: https://medium.com/@nusenu/how-malicious-tor-relays-are-exploiting-users-in-2020-part-i-1097575c0cac
A possible solution is to prohibit insecure connections through exit nodes. There are a couple of possible implementations:
-
HTTPS Everywhere has [https://www.eff.org/deeplinks/2018/12/how-https-everywhere-keeps-protecting-users-increasingly-encrypted-web EASE mode] that requires all connections to by HTTPS. If there's a website that doesn't support HTTP, it shows an error page and gives the user an option to continue or not. If there are HTTP subresources on any page, these are upgraded if possible and otherwise blocked.
-
Firefox has introduced an [https://bugzilla.mozilla.org/show_bug.cgi?id=1613063 "HTTPS-Only Mode"] that does the same thing. (It allows http://...onion connections, however.) This mode is still undergoing usability improvements, but these could likely be backported to ESR 78.
HTTPS support is much more pervasive on the web than in the past. I have been dogfooding HTTPS-Only Mode and it's remarkably rare to run into its error page.