SoylentNews is people
SoylentNews
from the what-browser-will-you-use-to-read-the-report? dept.
Eric Rescorla has a blog post over at Mozilla about the technical details on the recent Firefox add-on outage. He covers the background of how they use certificates, how they tried to mitigate the damage from the outage, how they worked to solve the problem without breaking more things, deployment of the replacement certificate, and why it took so long to fix.
Recently, Firefox had an incident in which most add-ons stopped working. This was due to an error on our end: we let one of the certificates used to sign add-ons expire which had the effect of disabling the vast majority of add-ons. Now that we've fixed the problem for most users and most people's add-ons are restored, I wanted to walk through the details of what happened, why, and how we repaired it.
There were a lot of work arounds discussed here and elsewhere, some of them quite stupid so, lastly, remember to undo any temporary work-arounds that might have been deployed last weekend.
Earlier on SN: In Firefox All Extensions Disabled Due to Expiration of Intermediate Signing Cert
(Score: 1, Informative) by Anonymous Coward on Friday May 10 2019, @11:18PM (2 children)
I did this one (to an older, ESR version):
In about:config, set this from true to false--
xpinstall.signatures.required;false
It let me run EFF Privacy Badger, which was all I wanted to add to FF anyway.
Does anyone have any reason why I shouldn't leave it this way, assuming I don't use any further extensions or add-ons?
(Score: 0) by Anonymous Coward on Friday May 10 2019, @11:34PM
Yes, that is also what I did. If I knew what that option did I would have switched it long ago.
(Score: 3, Interesting) by Anonymous Coward on Saturday May 11 2019, @12:02AM
This won't work after Mozilla uses Normandy to change your settings back to something they view as more secure.