On 04/05/2019 23.53, Dave Howorth wrote:
On Sat, 4 May 2019 22:27:18 +0200 "Carlos E. R." <> wrote:
On 04/05/2019 21.58, Dave Howorth wrote:
Help!
...
Does anybody know what has occurred or can suggest the best means to investigate further?
Firefox disabled all add-ons because a certificate expired <https://www.engadget.com/2019/05/03/firefox-extension-add-on-cert/>
The event occurred as the clock rolled over on UTC (Coordinated Universal Time, aka GMT or Greenwich Mean Time), and impacted users quickly narrowed it down to "expiration of intermediate signing cert" -- as it's described on Mozilla's bug tracker.
Thanks Carlos, and Brendan. I've now seen the Last Webkit Update thread.
I'm relieved that it's not some malware. But I'm puzzled about why it occurred on my machine so long after the problem is supposed to have arisen. Also about why it occurred since as I said, I run updates manually. Does FF have some secret private update mechanism?
Because it is not an update. It is a certificate in the chain of trust for addons that expired, a fact you can avoid by turning your clock back for days. Otherwise, at the exact minute the certificate expired, all the addons were automatically disabled. At least on restart of firefox, maybe even if you don't. My firefox is running fine, and I have a new addon I did not add myself: hotfix-update-xpi-intermediate 1.0.2 This is a hotfix that updates an intermediate certificate used for signing add-ons. It is one of the mechanisms used to fix bug 1548973. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org