←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: 0s | 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 #
_zephyrus_ ◴[04 May 19 08:55 UTC] No.19825299[source]▶
Firefox 66.0.3 here, and this has been the case also for me, i.e. everything is still working. After looking around for a while in bewilderment, I think that what's going is that they have remotely used the "studies" feature of Firefox to temporarily work around the problem.

Indeed, I see in about:studies,

hotfix-reset-xpi-verification-timestamp-1548973•Complete This study sets app.update.lastUpdateTime.xpi-signature-verification to 1556945257

(unfortunately I can not see when it was run in about:studies)

i.e. this "study" has reset the timestamp of the last signature verification to this morning (when I have started Firefox). Since I read around that Firefox performs the check only every 24 hours, I guess that this is reason why we have not been experiencing the problem. We have now another day, after which we will have to reset the timestamp again (if it has not been solved upstream). The field is available/accessible also in about:config.

P.S. To be fairly honest, I was a bit surprised about the "studies" feature, I can not recall when it was introduced, but it is probably my fault for having overlooked it.

replies(1): >>19825378 #
vatueil ◴[04 May 19 09:25 UTC] No.19825378[source]▶
Perhaps that's what Mozilla Add-ons was referring to when they tweeted:

https://twitter.com/mozamo/status/1124569680662777856

> We deployed a fix to users who hadn't had their add-ons disabled to make sure they saved that way. You're in that group. :)

replies(1): >>19825490 #
1. makomk ◴[04 May 19 09:59 UTC] No.19825490[source]▶
Of course, that fix only got to people who didn't disable the "studies" feature after Mozilla abused it to deploy a Mr Robot ad to all their users. Also, enabling it seems to require also agreeing to send telemetry information to Mozilla, so all the privacy-concious people who use extensions to protect their privacy will likely have it disabled as well.