On Sat, 4 May 2019 22:53:14 +0100 Dave Howorth <dave@howorth.org.uk> wrote:
On Sat, 4 May 2019 22:27:18 +0200 "Carlos E. R." <robin.listas@telefonica.net> 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?
Hmm, according to https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firef... "Clarified that the Studies fix applies only to Desktop users of Firefox distributed by Mozilla. Firefox ESR, Firefox for Android, and some versions of Firefox included with Linux distributions will require separate updates. (May 4, 12:03 EST)" So it sounds like we might need an update via openSUSE updates? (note that the option to allow Studies is not even enabled on my system, since I've configured it to not send data to mozilla) Also note that as I mentioned, I'm not applying most openSUSE updates at present (don't ask) so I would prefer that openSUSE send me a specific notice that the fix to this breaking bug is available if possible (and send my regards to the stupid people at mozilla for the hassle!) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org