Certain Firefox users may come across a message in the extensions panel indicating that their add-ons are not allowed on the site currently open. We have introduced a new back-end feature to only allow some extensions monitored by Mozilla to run on specific websites for various reasons, including security concerns.
What is this bullshit? Feel like this will lead to adblocks being blocked for certain websites under the guise of “security”, aka: we don’t have to justify shit to you.
It’s not going to inconvenience you that much, and the proof for that is that this has always been the case: extensions would never run on e.g. addons.mozilla.org. This makes sense; you don’t want extensions to trick you into installing other extensions, for example, or to hijack your sync password.
It looks like the main change is that this actually loosens this restriction: it looks like some trusted extensions from now on will be allowed.
I don’t know. Though, to my mind, Firefox has been all about tight defaults for everyone paired with a not-so-obvious opt-out for those who really need it.
That said I do understand the concern here. The page about quarantined domains doesn’t provide much details and it’s quite vague.
Oh come on, it’s still a free and open source browser. As seen in the other comments, it’s a badly worded security feature for firefox internal pages and mozilla pages.
It’s not going to kill adblock, it won’t send your data everywhere and it can be disabled through an option as well as by simply building firefox yourself.
Everybody should stop being so negative towards open source developers.
So it looks like it’s mostly to do with the account system of Firefox. I’m not sure why their websites would need special protection, but whatever. It’s not malicious, for now
Makes sense. You don’t want Addons to navigate to the addons page and install other addons. You also don’t want to give them access to the firefox sync data through your account to do the same from that end.
So allowing any random, possibly compromised, possibly installed by malware, add-on to run during the Firefox account login pages (see the list of URLs in this thread) isn’t a security concern to you?
The alternative would be to give addons so little permission that the damage wouldn’t matter.
Effectively break the whole system, i’m fine with the ignore list.
To me it sounds more like they plan on blocking all addons (other than some whitelist of “trusted” addons) on important pages (like the Google login page maybe?).
What is this bullshit? Feel like this will lead to adblocks being blocked for certain websites under the guise of “security”, aka: we don’t have to justify shit to you.
It’s not going to inconvenience you that much, and the proof for that is that this has always been the case: extensions would never run on e.g. addons.mozilla.org. This makes sense; you don’t want extensions to trick you into installing other extensions, for example, or to hijack your sync password.
It looks like the main change is that this actually loosens this restriction: it looks like some trusted extensions from now on will be allowed.
To disable “quarantined domains” if you have to : https://support.mozilla.org/en-US/kb/quarantined-domains
For how long are they gonna allow us to do that?
I don’t know. Though, to my mind, Firefox has been all about tight defaults for everyone paired with a not-so-obvious opt-out for those who really need it.
That said I do understand the concern here. The page about quarantined domains doesn’t provide much details and it’s quite vague.
1st thing to do on every release from now on.
This is a step too far for me. My device, my choice of browser and I am adult enough to make my own decisions.
Oh come on, it’s still a free and open source browser. As seen in the other comments, it’s a badly worded security feature for firefox internal pages and mozilla pages.
It’s not going to kill adblock, it won’t send your data everywhere and it can be disabled through an option as well as by simply building firefox yourself.
Everybody should stop being so negative towards open source developers.
Did everyone in this thread drink the conspiracy theory kool-aid or something? The accusations here are wild.
Is there even some way to see which addons this applies to on which websites? Or am I just going to find out randomly while browsing?
I was curious as well so I looked at the git tree. I’m not familiar with Firefox code, but I’m assuming I found the list:
pref("extensions.webextensions.restrictedDomains", "accounts-static.cdn.mozilla.net,accounts.firefox.com, addons.cdn.mozilla.net,addons.mozilla.org, api.accounts.firefox.com,content.cdn.mozilla.net, discovery.addons.mozilla.org,install.mozilla.org, oauth.accounts.firefox.com,profile.accounts.firefox.com, support.mozilla.org,sync.services.mozilla.com");From here
So it looks like it’s mostly to do with the account system of Firefox. I’m not sure why their websites would need special protection, but whatever. It’s not malicious, for now
Thanks! Nicer list:
Makes sense. You don’t want Addons to navigate to the addons page and install other addons. You also don’t want to give them access to the firefox sync data through your account to do the same from that end.
“Security concerns” is such a bullshit reason. If an add on is such a security concern, why host it in the first place?
I’m disappointed Mozilla is going down this path, but not surprised.
So allowing any random, possibly compromised, possibly installed by malware, add-on to run during the Firefox account login pages (see the list of URLs in this thread) isn’t a security concern to you?
The alternative would be to give addons so little permission that the damage wouldn’t matter. Effectively break the whole system, i’m fine with the ignore list.
To me it sounds more like they plan on blocking all addons (other than some whitelist of “trusted” addons) on important pages (like the Google login page maybe?).
at least it can be disabled in the prefs for now
I just hope that Librewolf will remove this.
You can always download the xpi and install it manually
this doesn’t block you from installing extensions. It blocks them from running on certain protected pages, whatever they may be