←back to thread

All extensions disabled due to expiration of intermediate signing cert

(bugzilla.mozilla.org)
1318 points xvector | 1 comments | 04 May 19 01:31 UTC | HN request time: 0.27s | source
Show context
lucb1e ◴[04 May 19 08:02 UTC] No.19825098[source]▶
If everyone's add-ons are disabled, I wonder why mine are not. My computer has been running over night (coincidentally, first time in years) and my add-ons are intact. Does it take a browser restart? Or might I have a setting that prevents this from happening? My system time is correct.

Edit: am on Firefox 66, Linux (Debian Buster/testing), using Firefox from Mozilla directly (not through repositories), and my internet/wifi should not have disconnected. System has been up since 2019-05-03T17:30:00Z, suspended before that.

replies(10): >>19825118 #>>19825121 #>>19825149 #>>19825157 #>>19825182 #>>19825186 #>>19825222 #>>19825225 #>>19825299 #>>19825337 #
Svip ◴[04 May 19 08:08 UTC] No.19825121[source]▶
I think it only checks at start up, or something? Mine has been running for days, and all my add-ons are working. As such, I've decided not to restart Firefox until news arrive that it's working again.
replies(2): >>19825127 #>>19825128 #
blahyawnblah ◴[04 May 19 08:10 UTC] No.19825127[source]▶
Mines been running for days and everything was disabled.
replies(1): >>19825131 #
1. lucb1e ◴[04 May 19 08:11 UTC] No.19825131[source]▶
Oh, darn. Thought I found a way to avoid this. Thanks for reporting!

Just a thought, might it be that you suspend (sleep mode in Windows) your system? So not restart the browser, technically, but iirc applications still receive some event when this happens. At the very least, open connections would break. Any TLS connection would re-validate the certificate. In that case, going offline would also trigger it. Have you done any of those (suspend, be offline / switch networks)?