{"id":9621,"date":"2019-05-04T10:40:18","date_gmt":"2019-05-04T08:40:18","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=9621"},"modified":"2024-10-03T00:38:44","modified_gmt":"2024-10-02T22:38:44","slug":"firefox-expired-certificate-disables-addons-may-4-2019","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/05\/04\/firefox-expired-certificate-disables-addons-may-4-2019\/","title":{"rendered":"Firefox: Expired certificate disables addons (May 4, 2019)"},"content":{"rendered":"

\"Mozilla\"[German<\/a>]Firefox users are currently suffer from a fat bug. The browser disables since May 4, 2019 suddenly extensions (Addons). Background is an expired certificate. Update:<\/strong> Mozilla has just released a fix that will be rolled out in the coming hours (see article end).<\/p>\n

<\/p>\n

Error: Addons suddenly no longer usable<\/h2>\n

\"\"German blog reader Guido B. already contacted me this morning by mail and shared his observations (thanks for that):<\/p>\n

I was badly surprised when I just opened my FF and saw my addons disabled. According to a message from FF my extensions are probably not compatible anymore? ?<\/p>\n

FF Version: 66.0.3 (64-Bit)<\/p>\n

My installed extensions: uBlock Origin \u2026.<\/p><\/blockquote>\n

For some entries there is a message like this::<\/p>\n

Skip Redirect CANNOT BE INSTALLED AND WAS NOT DEAKTIIVERT<\/p><\/blockquote>\n

Guido writes that he uninstall and reinstall Firefox. But that didn't help. If he tries to download and install one of the addons e.g. uBlock Origin now, the message \"Download failed. Please check your connection\" occurs – see the red bar in the following (German) screenshot.<\/p>\n

\"Firefox:<\/p>\n

Also my German blog post Firefox 66.0.3 freigegeben<\/a> got some user comments, reporting this bug (thanks to all for the feedback). On Bleeping Computer this forum post<\/a> deals with the bug – and in the social network Mewe.com I recognize the message this morning. Here is a screenshot of an addon status page in FF.<\/p>\n

\"Disabled
\n(Disabled addons, Source: Bleeping Computer forum)<\/p>\n

So something serious must have happened – and I didn't recognize, that Firefox has been updated this night.<\/p>\n

It's a bug: A certificate is expired<\/h2>\n

Some hours ago there was an entry All All extensions disabled due to expiration of intermediate signing cert<\/a> on Bugzilla with a rather banal explanation. A certificate simply expired.<\/p>\n

Steps to reproduce:<\/p>\n

Wait until it's past midnight on 2019-05-04 UTC.<\/p>\n

Actual results:<\/p>\n

All addons got disabled due not having valid signature.<\/p>\n

Expected results:<\/p>\n

If the signature was due to expire, it should have been renewed weeks ago. Not all extensions were disabled. Fakespot and Google Scholar Button were left in their disabled state.<\/p>\n

Some reports on reddit<\/a> 1<\/a> says that they had their clocks a day forward, but they may be just early canaries for the actual widespread issue.<\/p>\n

Going backwards in time allows installation from AMO but do not remove the unsupported mark from the add ons already installed.<\/p><\/blockquote>\n

Martin Brinkmann points this out on Ghacks.net (I noticed the post on Mewe.com), and at the same time provides an explanation. All Firefox extensions must be signed since Firefox 48 and Firefox ESR 52. Firefox blocks the installation of extensions with invalid or missing certificates.<\/p>\n

Since Mozilla's certificate has expired, this now causes problems in the clients. On reddit.com there is a mega thread<\/a> on the topic. Currently, users can probably do little – unless they work with Nightly Builds, where the certificate check can be turned off, as Martin Brinkmann writes.<\/p>\n

I found this reddit thread<\/a> where a user suggest to use about:config<\/em> to go to settings an set xpinstall.signatures.required <\/em>to false<\/em>. But my understanding ist, that this only helps in Firefox nightly builds.<\/p><\/blockquote>\n

According to this reddit thread<\/a> all we can do: Wait and be patient. Mozilla's developers are working on a fix.<\/p>\n

\n

So sorry for the issue we're having with add-ons right now!<\/p>\n

We're working hard to fix it and will keep you updated.<\/p>\n

\u2014 Firefox (@firefox) 4. Mai 2019<\/a><\/p><\/blockquote>\n