Live data from Hacker News

All extensions disabled due to expiration of intermediate signing cert

bugzilla.mozilla.org

501–510 of 955 posts

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

#502
post #394

What a spectacular failure... it's hours later, and still not working. The only thing firefox has going for itself stopped working. Already one family member and one friend switched to chrome.

Just switch for a day. You're making this out to be a much bigger issue than it has the capacity to be.

Many of us tech savvy Firefox users have told family and friends to use it as well. Mozilla's made us look like damn fools.

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

#504
post #390

What kind of idiot thought that the add-ons I have personally installed on my browser need to have a capability to be remotely disabled despite literally nothing being changed. This is absolutely inexcusable. I want to see everyone being responsible for this "verified add-ons" fiasco fired from the team (after they roll it back of course).

[deleted]

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

#505

Earlier quoted context omitted.

If you go to about:config and set "devtools.chrome.enabled" to true, the cmd-shift-j thing should work

I also have to do this to make it work on Win10 firefox console (F12)

If some addons DISAPPEARED then you have to restart Firefox, go to addon manager menu, find disappeared addons and disable/enable them.

When I say "disappeared" I mean that addon icon or else is disappeared.

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

#506
post #409

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 intern…

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…

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. :)

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

#508

Earlier quoted context omitted.

If you're going to quit anyway, and not saying this is a good idea, what prevents you literally going and yelling at these idiots demanding answers as to why they are not doing their jobs?

So many people have done this. Watch videos of past Mozilla All Hands meetings. You see the questions asked, you see the leaders dodge, and you see that soon after the askers are gone and leaders say- you have nothing to be afraid of, you don’t need to ask questions anonymously. “Executives” at 1000 person Mozilla are so distant from the workers, and middle managers listen to executives, not staff. It is so sad becau…

Sure, the organisation is far from perfect, and makes mistakes, but as a current Mozilla employee, I don't recognise this description.

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

#509

There's a workaround that involves going to about:config and setting xpinstall.signatures.required to false. However, if you're running the Stable or Beta version, it will only work under Linux. On Windows and MacOS you'll need to download Nightly or the Developer Edition. To fix this on MacOS I did the following: 1. Downloaded and installed Firefox Nightly 2. Ran /Applications/Firefox\ Nightly.app/Contents/MacOS/fir…

The following workaround works on regular editions: https://www.reddit.com/r/firefox/comments/bkhzjy/temp_fix_fo...

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

#510
I wonder how it's possible that these kinds of--I assume--easily preventable problems happen at huge corporations and projects.

I routinely renew certs for clients and it never happened that a website was down because of an expired cert.

I would think that Apple, Microsoft, Mozilla would be more efficient than me in avoiding these kinds of fuckups?

I also bet these companies make huge investments to their infrastructure so that their services have a near-100% uptime, and then they let certs expire.

Post reply on HN