{"id":33502,"date":"2019-10-31T21:52:58","date_gmt":"2019-10-31T18:52:58","guid":{"rendered":"https:\/\/prohoster.info\/blog\/segodnya-mnogie-populyarnye-addony-dlya-firefox-perestali-rabotat-iz-za-problem-s-sertifikatom\/"},"modified":"2019-10-31T21:52:58","modified_gmt":"2019-10-31T18:52:58","slug":"segodnya-mnogie-populyarnye-addony-dlya-firefox-perestali-rabotat-iz-za-problem-s-sertifikatom","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/segodnya-mnogie-populyarnye-addony-dlya-firefox-perestali-rabotat-iz-za-problem-s-sertifikatom","title":{"rendered":"Today, many popular add-ons for Firefox have stopped working due to certificate issues","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Hello, dear Habr users! <\/p>\n

I want to warn you right away that this is my first publication, so please notify me of any issues, typos, or anything else you notice.<\/i><\/p>\n

This morning, as usual, I turned on my laptop and started a leisurely surf in my favorite Firefox (version 66.0.3 x64). Suddenly, the morning ceased to be serene \u2014 at one unfortunate moment, a message popped up saying that some addons couldn't be verified and had been disabled. \"Great!\" I thought and delved into the addons control panel.<\/p>\n

<\/a><\/noindex>And\u2026 what I saw there somewhat shocked me, to put it mildly. All the addons were disabled. HTTPS Everywhere, NoScript, uBlock Origin, FVD SpeedDial, and several other addons that had been working perfectly until today were marked as outdated.<\/p>\n

My first reaction was, oddly enough, a housewife-like thought: \"A virus!\" However, common sense prevailed, and the first thing I did was try to restart the browser. Useless. I tried reinstalling the addons \u2014 I received a terse \u201cDownload failed. Please check your connection\u201d from the addon manager when attempting to install anything. \"Aha!\" I told myself and realized that the issue, apparently, wasn't with me<\/a><\/noindex>.<\/p>\n

Contacting my colleagues, I found out that they were experiencing the same issues with the browser. A quick Google search revealed a recent bug report on Bugzilla<\/a><\/noindex>, a small thread on Reddit<\/a><\/noindex> and this. a news item<\/a><\/noindex>As it turned out, starting today (May 4, 2019), extensions that have not received verification from Mozilla under their new rules<\/a><\/noindex>, which were supposed to be implemented in June, have stopped working as \"unsigned\". As it turns out, there were problems with the certificate on Mozilla's side that signed the extensions, and its validity period had expired.<\/p>\n

The cause of such a widespread failure \u2014 whether it was a bug on Mozilla\u2019s side, or a decision to \u2018proactively\u2019 block popular add-ons to force their re-verification under updated rules \u2014 is currently unclear. What is clear is that this issue will affect a vast number of users \u2014 after all, Firefox is primarily valued for its add-ons, so the consequences of today\u2019s failure are uncertain. But let's leave these speculations to analysts and couch experts, as a devoted user, I\u2019m primarily interested in when my extensions will be fixed. There is no answer to this question yet; I hope it happens as soon as possible. For now, the problem remains in a \u2018confirmed\u2019 status but is not yet resolved.<\/p>\n

As a workaround, switching to 'nightly' builds is suggested, where you can disable add-on checks, or some Manipulations<\/a><\/noindex> with the user profile (it didn\u2019t help me, unfortunately).<\/p>\n

Thank you to everyone who read this for your attention!<\/p>\n

UPD<\/b><\/a><\/noindex>: All users of the browser found their extensions blocked due to the expiration of the certificate used for generating digital signatures. As a workaround for restoring access to extensions, Linux users can disable digital signature verification by setting the \u2018xpinstall.signatures.required\u2019 variable to \u2018false\u2019 in about:config. This method works only in Linux for stable and beta releases; for Windows and macOS, a similar manipulation is only possible in nightly builds and in the Developer Edition. Alternatively, you can also change the system clock to a time before the certificate expiration <\/i>. Thank you for the addition rsashka<\/a><\/noindex>!<\/p>\n

UPD2<\/b>: I added a poll (not sure why I didn\u2019t think to do this right away) to see how widespread the issue is.<\/p>\n

UPD3<\/b>: Thank you AnatoliyTkachev<\/a><\/noindex> for the reference to guide<\/a><\/noindex> for the workaround. I solved the problem with a script, as it required the least effort.<\/p>\n

UPD4<\/b>: the developers wrote<\/a><\/noindex>, who have developed a temporary solution<\/p>\n

Only registered users can participate in the survey. Please log in<\/a><\/noindex>, please.<\/p>\n

Have you encountered any issues with Firefox extensions?<\/h2>\n