Duplicate of this bug
All extensions disabled due to expiration of intermediate signing cert
401–410 of 955 posts
Re: All extensions disabled due to expiration of intermediate signing cert
#402Earlier quoted context omitted.
I had the same thought, but I still find that absurd. Say they host 500,000 websites with HTTPS. 1,000,000 renewals they save spread across the year, roughly 2 renewals a minute. That is pennies. A t2.medium could handle that type of load increase
A bit OT, but what's up with this usage of Amazon EC2 tiers as a unit of computational power?
i think it’s a combined “fixed cost” rather than just computational power... like you could do it with x, thus it should cost at most y
similar to saying that you could do it with a raspberry pi
Re: All extensions disabled due to expiration of intermediate signing cert
#403Looks like all extensions have been disabled for all Firefox users. I think this fail-closed behavior is more of a security issue than the one it is trying to solve. All of my security add-ons - Privacy Badger, NoScript, Decentraleyes, and many more were disabled. Even worse, it happened without notice to the user. One moment I was browsing the internet (just barely) secured by these add-ons, and the next moment, all…
If it failed open, anyone unlucky enough to update their extensions could end up having a malicious version installed. It also would have taken longer to notice.
It should fail 'locked'. continue to allow installed addons to work, notify the user of issue, disable any updates without explicit request by the user.
Re: All extensions disabled due to expiration of intermediate signing cert
#404What 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).
remotely disabled
As I understand it, the browser checks the certificate of add-ons at some point (on startup? on an interval?) and only uses signed ones. And since signatures are date restricted, previously valid signatures can become invalid.
I'm not 100% sure if this really is the mechanism. Would be interesting to hear from someone in the know.
Re: All extensions disabled due to expiration of intermediate signing cert
#405There have been major organizational problems at Mozilla for a long time that precipitated this. Many of us saw something like this coming, saw gaps and unclear responsibilities, reported these gaps and confusions up the chain, and were reprimanded and financially penalized for asking the tough questions. The questions were never answered, and we all quit, were fired, or lost motivation as a result.
This is a tech problem, yes. Cert renewal has bitten everyone in a high profile way (apple, google, and ms have all had renewal-related outages in recent years). But this was preventable at Mozilla. Ask a Mozillian about IT and Cloud Sevices, and what their respective responsibilities are. Ask Mozilla’s VP of IT- who is responsible for cert renewal? Ask Mozilla leadership- why are people afraid to ask questions?
Re: All extensions disabled due to expiration of intermediate signing cert
#406What 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
#407To re-enable all disabled non-system addons you can do the following. I am not responsible if this fucks up your install: Open the browser console by hitting ctrl-shift-j Copy and paste the following code, hit enter. Until mozilla fixes the problem you will need to redo this once every 24 hours: // Re-enable *all* extensions async function set_addons_as_signed() { Components.utils.import("resource://gre/modules/addon…
This worked like a charm. Thanks very much!
Re: All extensions disabled due to expiration of intermediate signing cert
#408[deleted]
Re: All extensions disabled due to expiration of intermediate signing cert
#409If 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.
Re: All extensions disabled due to expiration of intermediate signing cert
#410Earlier quoted context omitted.
Seems like an over-reaction. "Destroy user trust in Mozilla?" Really? Because your extensions got disabled for a day?
Users will drop a product for the slightest reason. For instance, one of our users recently left a negative review. Paraphrasing, "Logging in is difficult". We check our warning system (set up to detect suspicious logins, incidentally also catches any users who've been locked out because they forgot their password), and his last login attempt took a total of two tries.
Honestly then he is just an idiot and he will come back when he realizes he has to login to other services too.