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?
The same sh*t with me, I restarted Firefox process, after restore my session, all addons disabled by default without any option, you know: I know the risk, and accept it
Fun fact: This happened on one machine of several running Firefox. No idea why. Need to go deeper into configs and break more stupid crap? I wonder if copying over configs from a working machine would fix it. Blech.
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...
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.
The "fix" in the second link is amusing. The user had the clock wrong so the bug hit sooner. Adjusting the clock to the correct time "fixed" it but the issue is probably now back. Too bad there wasn't a root cause analysis of that failure. We wouldn't be having the widespread issue.
Somebody somewhere is going to feel silly and shamefully flip the 'more magic' switch back, or so I suspect.
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.
What's there to trust in Chrome? Google not only gets to see everything you are doing that interests them in the browser but also refuses to allow full functionality and/or use of various extensions (depending on the extension) that are available in firefox. Besides, would you trust a browser by a corporation who tries to hinder those who seek to take control over their mobile devices, try to get spyware into everything and has their search engine programmed to allow them to decide what information you have access to on an individual basis to only let you know what they feel you should know?
Firefox is about to lose a ton of its users over this. I saw this on a family member's computer just now, couldn't get ublock origin installed or any extension for that matter. Had to install Chrome for them.
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.
Restarting Firefox is not necessary for this to happen. It happened to me while streaming video a few minutes ago. I use containers and I was logged out of my account, since containers were disabled.
I think this fail-closed behavior is more of a security issue than the one it is trying to solve. All of my security add-ons - Privacy Badger, NoScript, Decentraleyes, and many more were disabled. Even worse, it happened without notice to the user.
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.
I love my privacy too but you’ve got to keep the magnitude of things in mind. Those extensions are making it harder to correlate your interactions with different companies, this fail-closed behavior is protecting you against criminals gaining access to all your online accounts.
Bullshit. Those extensions protect against both. Javascript being an important criminal vector. This fail-closed behaviour is disabling certified code because of an arbitrary date. At time of install the code was verified.
The code didn't change since. Mozilla is stupid for doing this.
> for better or worse, google chrome team would never let something like this happen
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.
That was only in one timezone, on a VERY old Android build, and not a clearly obvious bug.
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.
Major bugs like this are uncommon but they happen. I know they're working on the fix. There is nothing more they could do than to fix the issue and prevent it from happening again.
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.
Same problem here all my extensions now are gone. I just encountered that issue early in this morning. Tried to find a solution on how to fixed it in the internet but issue stil there i format also my laptop but nothings happen. FF should make a move about this problem they will lost a lot of customers about this one.
I think not all mozilla users are having this kind of problem right now.I tried to install add-ons on my other laptop and made it. So i guess some users only are infected by this issue
117 comments
[ 2.9 ms ] story [ 165 ms ] threadIt'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...
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.
https://github.com/mozilla/addons/issues/978
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.
https://bugzilla.mozilla.org/show_bug.cgi?id=1548973
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.
all time firefox user here
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.
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.
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.
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.
never use chrome, ie, saffari and variants.
After this,
i will continue to favour firefox and pick it instead of other browsers.
every project can have its slump.
Throw the rock all your projects had success.
Long life firefox !!! Please fix this asap!