Live data from Hacker News

All extensions disabled due to expiration of intermediate signing cert

bugzilla.mozilla.org

531–540 of 955 posts

Re: All extensions disabled due to expiration of intermediate signing cert

#531

Update: We have rolled out a partial fix for this issue. We generated a new intermediate certificate with the same name/key but an updated validity window and pushed it out to users via Normandy (this should be most users). Users who have Normandy on should see their add-ons start working over the next few hours. We are continuing to work on packaging up the new certificate for users who have Normandy disabled.

Is it weird that this problem only happened to me (add ons all being disabled) roughly 10 minutes ago?

I was browsing fine this morning for maybe four hours and now all my plugins/addons are gone.

Re: All extensions disabled due to expiration of intermediate signing cert

#532

Update: We have rolled out a partial fix for this issue. We generated a new intermediate certificate with the same name/key but an updated validity window and pushed it out to users via Normandy (this should be most users). Users who have Normandy on should see their add-ons start working over the next few hours. We are continuing to work on packaging up the new certificate for users who have Normandy disabled.

Thanks. This must be terribly stressful to you.

Meanwhile, having to browse the web without an adblocker has been nothing but relaxing for everybody else.

Re: All extensions disabled due to expiration of intermediate signing cert

#533
post #225

Just discovered the same message in the Tor browser, and it seems that NoScript got disabled. So people running Tor are a lot more vulnerable right now. Also, wow, the web has a ton of ads. I've been running uBlock origin so long I forgot how bad it had gotten :(

> Also, wow, the web has a ton of ads. I've been running uBlock origin so long I forgot how bad it had gotten :( Try turning it off. I got rid of ublock after arstechnica complained about a lot of their users blocking ads years ago and it honestly isn't that bad. Every once in a while I do back out of a page for maxing out one of my cpu cores but otherwise, nothing ever bad happens. With ads: either it takes me half…

[deleted]

Re: All extensions disabled due to expiration of intermediate signing cert

#534

This is why users need to be in control of their own computers. Why can't I tell my copy of Firefox to ignore the certificate? Why can't I sign my own extensions? Mistakes happen, it's okay. But users should be empowered to work around them.

> Why can't I tell my copy of Firefox to ignore the certificate? Why can't I sign my own extensions? The issue is that if you leave any sort of lever that reduces security, it will be abused by bad actors. This is why browsers are having ever decreasing ways to bypass security and have full access. It is annoying, but at the end of the day, protecting 99.999% of the users trumps what us power users want.

> The issue is that if you leave any sort of lever that reduces security, it will be abused by bad actors.

As you can see in this discussion, there already are some obtuse ways to disable/ignore the signing. It's just way worse if people have to disable the signing instead of adding a trust for their own certificate, so that only mozilla and user's addons are truste instead of all the malicious garbage out there on the web.

Re: All extensions disabled due to expiration of intermediate signing cert

#535

Earlier quoted context omitted.

So is that a backdoor into my prefs? How can I check if Normandy is active on my installation?

Type about:config in the address bar and search for 'app.normandy.enabled' flag.

here the flag is true but the extensions are still unsupported

Re: All extensions disabled due to expiration of intermediate signing cert

#536

Update: We have rolled out a partial fix for this issue. We generated a new intermediate certificate with the same name/key but an updated validity window and pushed it out to users via Normandy (this should be most users). Users who have Normandy on should see their add-ons start working over the next few hours. We are continuing to work on packaging up the new certificate for users who have Normandy disabled.

Is it weird that this problem only happened to me (add ons all being disabled) roughly 10 minutes ago? I was browsing fine this morning for maybe four hours and now all my plugins/addons are gone.

The check is done every 24 hours and it seems for you these 24 hours were over roughly 10 minutes ago.

Re: All extensions disabled due to expiration of intermediate signing cert

#537

Just discovered the same message in the Tor browser, and it seems that NoScript got disabled. So people running Tor are a lot more vulnerable right now. Also, wow, the web has a ton of ads. I've been running uBlock origin so long I forgot how bad it had gotten :(

[deleted]

Re: All extensions disabled due to expiration of intermediate signing cert

#538

Earlier quoted context omitted.

So is that a backdoor into my prefs? How can I check if Normandy is active on my installation?

Type about:config in the address bar and search for 'app.normandy.enabled' flag.

Well that's interesting. I see Normandy enabled, but if I go to the "Privacy and Security" section of the preferences page I see all the data collection and use stuff disabled. There's no obvious way to disable the Normandy back door.

Oh well, at least we don't have another season of Mr Robot spam to look forward to.

Re: All extensions disabled due to expiration of intermediate signing cert

#539

Update: We have rolled out a partial fix for this issue. We generated a new intermediate certificate with the same name/key but an updated validity window and pushed it out to users via Normandy (this should be most users). Users who have Normandy on should see their add-ons start working over the next few hours. We are continuing to work on packaging up the new certificate for users who have Normandy disabled.

Is it weird that this problem only happened to me (add ons all being disabled) roughly 10 minutes ago? I was browsing fine this morning for maybe four hours and now all my plugins/addons are gone.

No, because the browser only checks for updates to your addons every day or so, not every five seconds.

Re: All extensions disabled due to expiration of intermediate signing cert

#540

Update: We have rolled out a partial fix for this issue. We generated a new intermediate certificate with the same name/key but an updated validity window and pushed it out to users via Normandy (this should be most users). Users who have Normandy on should see their add-ons start working over the next few hours. We are continuing to work on packaging up the new certificate for users who have Normandy disabled.

Is it weird that this problem only happened to me (add ons all being disabled) roughly 10 minutes ago? I was browsing fine this morning for maybe four hours and now all my plugins/addons are gone.

No. That’s not weird. The validity check runs once a day.
Post reply on HN