Make sure users cannot install additional https-everywhere extensions
We should think about the scenario where users think that HTTPS Everywhere is not installed in Tor Browser, and install it manually (either via AMO or EFF webpage). To avoid possible conflicts with the built-in HTTPS Everywhere we may want to prevent users from installing this extension manually.
Activity
Yes please. The best plan would be to somehow recognize the attempt and stop it, plus also educate the user that https-everywhere is already installed, we just hid it from the toolbar.
And an ok backup plan would be to survive having the attempt happen, that is, it's fine if a new install succeeds, so long as it doesn't ruin our settings or safety.
changed milestone to %Tor Browser: 10.5
mentioned in issue #40118 (closed)
added Backlog label
changed milestone to %Tor Browser: 11.0 Issues with previous release
marked this issue as related to #40458 (closed)
marked this issue as related to #40846 (closed)
added Roadmap::Future label and removed Backlog label
@gaba is this ticket still an issue? HTTPS-Everywhere is removed with the move to HTTPS-Only Mode
FWIW, android also has HTTPS-Only mode available, since v100 - https://support.mozilla.org/en-US/kb/https-only-mode-firefox-android
