Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 15 submissions in the queue.
posted by mrpg on Saturday May 04 2019, @04:46AM   Printer-friendly
from the FFS! dept.

Armagadd-on 2.0, Mozilla expired certificate disables add-ons

No, the culprit you are losing add-ons isn't your computer, or maybe your old FF, or dropping of Webextensions API. Twitter, Reddit, everyone is wondering what is going on. This Armagadd-on 2.0 has a simple explanation: Mozilla forgot to renew certificates, and so add-ons are failing like if they were not properly signed, because technically they are not. Even signing of new add-ons is down (see comment 9). Great weekend at Mozilla HQ!

Some workarounds, until they clean up the mess, include playing with the computer clock (NTP? forget it) or disabling signature checks (not possible in default releases).

All Firefox extensions disabled due to expiration of intermediate signing cert

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0

Steps to reproduce:

Wait until it's past midnight on 2019-05-04 UTC.

Actual results:

All addons got disabled due not having valid signature.

Expected results:

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.

Some reports on reddit says that they had their clocks a day forward, but they may be just early canaries for the actual widespread issue.

Going backwards in time allows installation from AMO (Mozilla Add-ons) but do not remove the unsupported mark from the add-ons already installed.

https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

Workaround: Go to about:config and set xpinstall.signatures.required to false


Original Submission #1Original Submission #2

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 5, Interesting) by jmorris on Saturday May 04 2019, @06:49PM (1 child)

    by jmorris (4844) on Saturday May 04 2019, @06:49PM (#838923)

    My normie existence has been split between Seamonkey and Firefox for some time now. Thinking it is time to push the migration schedule up to "ASAP." Dissident life has been on and off with Brave for some time, it keeps getting better and more suitable as a default browser. Chrome is of course a non-starter.

    Bottom line. We should have seen the writing on the wall with Moz Corp a few years ago, a lifetime of familiarity and goodwill with Netscape and Mozilla's children have lead us to greatly underestimate the danger they have become. The only reason Google is more dangerous is the nearly Trillion dollar market cap they can wield, which has allowed them to push Moz out of the way. But we need to wake up, lose the attachment to what they once were and let them die; for if they ever did write a new chapter in the Book of Mozilla, if they had another rebirth it would be in an awful and terrible form. The lizard has gone bad, we have to put it down, out of love for what it once stood for. Let not future generations remember Mozilla only for its modern sad and evil form in its twilight, let it be remembered as a powerful symbol of the first great age of the Internet. Let him be remembered for standing proudly and roaring his mighty challenge at Mammon.

    Starting Score:    1  point
    Moderation   +3  
       Troll=1, Insightful=1, Interesting=2, Informative=1, Total=5
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   5  
  • (Score: 2) by urza9814 on Monday May 06 2019, @02:21PM

    by urza9814 (3954) on Monday May 06 2019, @02:21PM (#839617) Journal

    The problem with Brave is that it cements Google's control over the web -- it's just one more Chrome clone.