Firefox Disabled All My Extentions
I opened Firefox and all of my extensions are disabled saying One or more installed add-ons cannot be verified and have been disabled. Is anyone else experiencing this?
Cannot tell if it's related to https://www.reddit.com/r/firefox/comments/bjwz8n/addon_polic... (Says new Add-On Policy effective June 10th, 2019, so shouldn't be causing this. But...)
As mentioned elsewhere, seems like when your clock hits 5/4 midnight UTC, you're done. I tried setting my clock in the past, but that did not fix the issue for me. (Clock was previously auto w/ daylight savings time enabled.)
Super interesting to watch /r/firefox go from 3.8k active/online users to 5.6k over the past half hour...
Edit: As mentioned below, there are GitHub/Bugzilla entries. They seem to be aware and starting to work towards a fix, though the explanation of the problem hasn't emerged yet.
Clearly resetting your date is a "fix" in the temporal sense that it works until you apparently hit the magic deadline again, but I'm curious why this only hit one of my machines. Pretty sure I was running the same FF version on both, but not certain. Again wondering if it's due to a difference in the configs, since I've 'modified' those at different times with different lists of needless crap to disable.
It's not like I was running an old version of FF with XUL extensions or anything like that, either - latest version, addons properly signed, all added from Mozilla site.
On top of that, attempts to re-add extensions via https://addons.mozilla.org result in "Download failed. Please check your connection." errors. This makes me suspect that there's something up with Mozilla inf.
There are definitely some good arguments in favor of Mozilla-signed addons, but events like this that expose an (apparent) SPoF are less than great. If only running one of the Firefox forks didn't involve getting security patches late...
It's a signing cert failure, not an intentional move. Still... this is going to destroy user trust in Firefox.
The bug name ("armagadd-on" 2.0) is quite fitting :)
This is not an intentional move, shit happens. I wouldn't lose trust so quickly. They're trying to make addons more safe and secure.
One moment I was browsing the internet (just barely) secured by these add-ons, and the next moment, all of them disappeared (without warning) and I only noticed when I saw my password manager was missing.
The code didn't change since. Mozilla is stupid for doing this.
No, this is not a reason.
This has to be some type of a bug, every extension gets disabled with zero notice and cannot be re-downloaded.
I'm not seeing it myself yet, but haven't restarted firefox in a few hours.
Has anyone tried disabling xpinstall.signatures.required in about:config? Saw someone mention it elsewhere, but didn't try it in time.
All of my legacy extensions are disabled. My beloved uBlock Origin included. Only Disconnect works. Tried downloading alternatives and can't even do that; keep getting a "download failed. Check your connection." The hilarious part, they said the new add-on signing doesn't affect themes, so why are nine of my themes disabled? It's getting old, all this messing with stuff all the damn time. I don't need you to hold my hand, Firefox.
If I want to run add-ons that don't use Web API then let me do it to my own detriment...
If you use Android, you can get Fennec from the F-Droid online store.
If you use Windows, you can get Waterfox here: https://www.waterfox.net/
Fennec is just a fork of Firefox with telemetry disabled by default and known third party trackers removed.
Waterfox is a fork of Firefox that tries to be more geared toward users who want more control, its main differences are telemetry is disabled by default and it is supposed to support more extensions but I have not tested this out.
I understand about the 'safety issue', but I think people are more mad about their extensions disappearing than they were about the 'safety' of the extensions themselves.
In my opinion, a better way to implement the signature extensions would have been to give users a pop-up or something that said:
"The following extensions do not have a signature from Mozilla. [List user's extensions that don't have a signature.] This means that they may be more unstable or they may not be safe (or as safe) as using an extension that has a verified signature. Would you like to continue using these extensions? {Yes} {No} Mozilla is not responsible for any breached data as a result for using unverified extensions, blah, blah, blah, disclaimer stuffs."
That way Mozilla wouldn't have to be concerned that they would get in trouble for whatever it is that they are worried about, and people could still have their extensions.
Sooo............
Is Firefox now going into everyone's browsers and reseting what they don't like and making you doing things their way now????
If so, time to get a new browser if they are going on to Peoples PC's, even those who set them to not update, and forcing changes. I thought MS was bad with what they do, but now Firefox is reseting my browser remotely??? :(
Windows 10/FF 56 setting extensions.legacy.enabled, true and xpinstall.signatures.required, false doesn't work but does in Linux Mint 19/FF 66 does.
We also added app.update.auto, false to stop Firefox from auto-updating untill they un-F this mess
By the way, the "hot-fix" doesn't work for Win10/FF 56
hotfix-update-xpi-intermediate%40mozilla.com-1.0.2-signed.xpi
A fix? votes out, this could very well be temporary...but my customization is gone/reset, so there's that bit of nuisance.
try it if still stuck.
https://support.mozilla.org/tr/kb/reset-preferences-fix-prob...
user_pref( "extensions.legacy.enabled", true );
user_pref( "xpinstall.signatures.required", false );
I was on ESR versions for a long time. Damn Firefoix, why'd you do this?! We have already FOUGHT it off once!
Many thanks - otherwise a great product, is FireFawx
I also can't set my New Tab to go to google anymore.
Good thing Firefox isn't my only browser.
A few years ago, Chrome crashed for everyone on the date daylight saving time started (a quick search tells me it probably was https://bugs.chromium.org/p/chromium/issues/detail?id=287821). So not only would they let something like this happen, it did already happen.
Forcing signing by one key, with no way to disable it literally screams "THIS WILL BACKFIRE"
In fact when Mozilla initially proposed this, they were told this would happen by many users. They ignored that warning x claiming they knew better. The rest is history.
Users can't inspect the code or contribute to the code, which is what addons used to do.
Arman.
I also can no longer set my new tab feature to go to google.
I noticed this in anytime Ive used Chrome in the past, and it's only been on a FF issue that has me scrambling for a temporary replacement.