Live data from Hacker News

All extensions disabled due to expiration of intermediate signing cert

bugzilla.mozilla.org

491–500 of 955 posts

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

#491
post #487

Earlier quoted context omitted.

You basically just described any sufficiently large organization. Complaining is not helping anyone in these situations, the only thing you can do to change things is to go ahead and try to change things. Reporting things up the chain hardly ever works because the chain is too busy with their own issues and politics. You have to make it worth their while.

> You have to make it worth their while. Not having a large outage seems like it should be worth their while...

Outages like this never seem real until they actually happen.

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

#493
post #458

Run this in your Browser Console[1] to delay signature checking for a day: function set_xpi_sign_time_now() { const {Services} = ChromeUtils.import("resource://gre/modules/Services.jsm"); const now = (new Date()).getTime() / 1000; Services.prefs.setIntPref('app.update.lastUpdateTime.xpi-signature-verification', now); } set_xpi_sign_time_now(); EDIT: Changed `Components.utils.import` to `ChromeUtils.import` because ap…

Outside of about:addons I get this in Firefox 66.0.3 in Linux: > ReferenceError: ChromeUtils is not defined Also, this doesn't seem to help with currently disabled add-ons, unless I'm missing something. Trying to reinstall Adblock Plus, for example, still results in > Download failed. Please check your connection.

> Outside of about:addons ...

You seem to be trying in a standard Web Console, not the Browser Console.

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

#494

There 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 pr…

I feel you. I saw this kind of thing coming back in 2010, when Firefox started copying Chrome blow for blow. I saw Google's influence on Mozilla and knew it could only turn out poorly. By the way, what can you say about that?

Maybe before talking about this he\she should provide any kind of proof of ever working at Mozilla at all?

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

#495
post #458

Run this in your Browser Console[1] to delay signature checking for a day: function set_xpi_sign_time_now() { const {Services} = ChromeUtils.import("resource://gre/modules/Services.jsm"); const now = (new Date()).getTime() / 1000; Services.prefs.setIntPref('app.update.lastUpdateTime.xpi-signature-verification', now); } set_xpi_sign_time_now(); EDIT: Changed `Components.utils.import` to `ChromeUtils.import` because ap…

Outside of about:addons I get this in Firefox 66.0.3 in Linux: > ReferenceError: ChromeUtils is not defined Also, this doesn't seem to help with currently disabled add-ons, unless I'm missing something. Trying to reinstall Adblock Plus, for example, still results in > Download failed. Please check your connection.

Beginning in Firefox version 52 released March 7, 2017, installed NPAPI plugins are no longer supported in Firefox, except for Adobe Flash. Some of the plugins that no longer load in Firefox, even though they may be installed on your computer, include Java, Microsoft Silverlight and Adobe Acrobat. See this compatibility document for details. https://support.mozilla.org/en-US/kb/npapi-plugins?as=u&utm_...

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

#496
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.

it's not about me. I can fix this for me. But most people can't. And for them, basically their computer stopped working right.

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

#497

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…

Thank you for speaking out here! I hope that mozilla employees manage to free themselves from their leadership and change the organization from within. It's possible, even though most employees who could change something have decided to simply leave over the years. Maybe mozilla needs a stark revenue drop to get humble again?

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

#498

Honestly, I just have to wonder what the Mozilla devs do. Don't they use extensions? Didn't they notice what was going on? Why does it increasingly feel like a more random Google Chrome-Lite paired with Apple's 'best intentions'?

This is a certificate that expired, not some insufficiently-tested change someone deployed. Mozilla devs had their extensions disabled at the same time as everyone else.

Well, most of the actual developers probably run Daily and have xpinstall.signatures.required = false, and are therefore not impacted quite as severely.

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

#500
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…

Same thing here, I'm on 66.0.3 and I booted the PC 2h ago but I still have everything working properly.

Only reason I've heard of it is because my dad calling me in "panic", it seem to affect both his PC.

Post reply on HN