Some Firefox customers began to note that put in browser extensions have been all disabled within the net browser instantly. Extensions would show “couldn’t be verified to be used in Firefox and has been disabled” messages within the add-ons supervisor of the browser. Firefox would show “One or extra put in add-ons can’t be verified and have been disabled” on the prime as a notification subsequent to that.
Affected extensions embody LastPass, Ghostery, Download Manager (S3), Dark Mode, Honey, uBlock Origin, Greasemonkey, NoScript, and others.
Update: Mozilla began to roll out a repair for Release, Beta, and Nightly variations of Firefox. The repair makes use of Mozilla Studies, and it’s good to make it possible for that is enabled to get it. Mozilla notes that you could be disable Studies once more after the repair is utilized and add-ons have been re-enabled. You must make it possible for “Allow Firefox to put in and run research” is checked on about:preferences#privateness. End
Only choices offered have been to search out a alternative and to take away the extension in query; this left affected customers puzzled. Was this some sort of preemptive strike against policy violation extensions? Mozilla did announce that it might implement insurance policies extra strictly.
The reply is not any. Turns out, the difficulty is attributable to a bug. If you learn fastidiously, you discover that verification is the difficulty. A brand new thread on Bugzilla means that this has one thing to do with extension signing.
Firefox marked addons due signing as unsupported, however would not permit re-downloads from AMO → All extensions disabled because of expiration of intermediate signing cert.
All Firefox extensions must be signed since Firefox 48 and Firefox ESR 52. Firefox will block the set up of extensions with invalid certificates (or none), and that’s inflicting the difficulty on person techniques.
Related points have been reported: some users can’t set up extensions from Mozilla’s official Add-ons repository. Users get “Download failed. Please verify your connection” errors once they try to obtain any extension from the official repository.
Nightly, Dev and Android customers might be able to disable signing of extensions; some customers reported that this resolved the difficulty quickly on their finish. You must set the choice xpinstall.signatures.required to false on about:config to disable signing. You may change the system date to yesterday to resolve it quickly as nicely, however that may result in different points.
The difficulty can solely be resolved on Mozilla’s finish. The group must renew the certificates or create a new one to resolve the difficulty. I would count on Mozilla to do this quickly as the difficulty is widespread and affecting a number of Firefox customers.
Users mustn’t take away affected extensions from their installations; the difficulty will resolve itself as soon as Mozilla fixes it.