Hello, dear Khabrovites!
I want to warn you right away that this is my first publication, so I ask you to immediately notify me of any problems, typos, and so on.
In the morning, as usual, I turned on the laptop and began leisurely surfing in my favorite Firefox (release 66.0.3 x64). Suddenly, the morning stopped being languid - at one beautiful moment, a message popped up that some addons could not be checked and were disabled. "Wonderful!" I thought and got into the addons control panel.
And ... what I saw there shocked me somewhat, to put it mildly. All addons are disabled. HTTPS Everywhere, NoScript, uBlock Origin, FVD SpeedDial and a few other add-ons are marked as obsolete, which worked without any problems until today.
The first reaction was, oddly enough, the thought a la housewife: "Virus!". However, common sense prevailed, and the first thing I tried was restarting the browser. Useless. I tried to reinstall the addons - I got a laconic "Download failed. Please check your connection" from the add-on manager when trying to install anything. "Aha!" - I said to myself and realized that the problem, apparently, .
Having contacted colleagues, I found out that they also have the same problems with the browser. Quick googling came up with , small and like this . As it turned out, as of today (4.05.2019/XNUMX/XNUMX), extensions that have not received verification from Mozilla on their , which were supposed to be introduced from June, stopped working as "unsigned". As it turned out, there were problems with the certificate on the Mozilla side, with which the extensions were signed, its validity period had expired.
What caused such a massive failure - some kind of bug on the side of Mozilla, or the decision to "preventively" block popular add-ons in order to force their re-verification according to the updated rules - is still unclear. It is clear that this problem will affect a huge number of users - after all, Firefox is valued, first of all, for addons, so it is not clear what consequences today's failure will have. But let's leave these thoughts to analysts and couch specialists, and as a dedicated user, I'm primarily interested in when my additions will be fixed. There is no answer to this question yet; I hope this happens as soon as possible. While the problem is in the status of "confirmed", but not fixed.
So far, as a crutch, it is proposed to switch to βnightlyβ builds, where you can disable checking for addons, or some with a user profile (personally, unfortunately, it did not help me).
Thank you all for your attention!
: For all browser users, the add-ons were blocked due to the expiration of the lifetime of the certificate used to generate digital signatures. As a workaround for Linux users to regain access to add-ons, digital signature verification can be disabled by setting the "xpinstall.signatures.required" variable in about:config to "false". This method for stable and beta releases only works on Linux, for Windows and macOS, such manipulation is possible only in nightly builds and in the Developer Edition. Alternatively, you can also change the value of the system clock to the time before the certificate expires . Thanks for the addition !
UPD2: Added a poll (not sure why I didn't think to do it right away) to see how widespread the problem is
UPD3: Thank you for a link to bypassing the problem. For myself, I solved the problem in a way with a script, as requiring the least gestures.
UPD4: developers that developed a temporary solution
Only registered users can participate in the survey. , you are welcome.
Are you having problems with Firefox extensions?
-
Yes, Firefox Quantum release version
-
Yes, Firefox Quantum nightly/developer version
-
Yes, Firefox for mobile OS
-
Yes, Firefox ESR
-
Yes, Firefox based browser (PaleMoon, Waterfox, Tor Browser etc.)
-
No
1235 users voted. 234 users abstained.
Source: habr.com