Live data from Hacker News

All extensions disabled due to expiration of intermediate signing cert

bugzilla.mozilla.org

781–790 of 955 posts

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

#781

Certificates have been in common use online for maybe two decades now, if not more. This is a common failure mode and it keeps happening. Is there some fix so we don’t have to keep dealing with spontaneous failures due to expirations? Or are we doomed to suffer with this until the end of time?

Use a certificate monitor https://letsmonitor.org (free)

Is that site legit? Why don't they even have a HTTPS redirect?

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

#782
post #227

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

I used this code and it worked. However, I just received Mozilla fix. Do I need to now delete this code from the browser console?

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

#783
post #567

Earlier quoted context omitted.

That does nothing to mitigate the wholesale disabling of already trusted plugins like uBlock.

Well, if you follow the OP, you'll realize that it's a bug and people are working to fix it :)

The bug is that plugins can't be manually enable. Nobody is working to fix that.

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

#784
post #656

Earlier quoted context omitted.

app.normandy.enabled That is not what I meant by a UI knob, and I sure hope you knew that. By UI knob I mean something easily discoverable and self-explanatory. Rooting around a gated (with a mighty strong warning, I should add) config section for something called "normandy" is not intuitive, and it's not self-explanatory. And I sure hope that by disclosed to users I did not mean some Hitchhiker's Guide-esque disclai…

I'm sorry to break it to you, but a fuckton is not actually part of the metric system...

This unit modifier was specified under RFC 69420

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

#785

Earlier quoted context omitted.

With an obscure name and no correlation to all the other spying and backdoor ING Mozilla are doing. Is this really the best option tog etaprivacy focused browser? I think this is all very worrying.

Can you elaborate on what 'other spying' Mozilla does? Do you mean their telemetry?

Spying was the wrong word. But yes, the telemetry. The google analytics that are hidden on the extensions page, that only listen to the Do not track, but not the turn off telemetry checkbox. Sadly it just doesn't seem to stop.

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

#786
post #704
post #592

Earlier quoted context omitted.

JSON response from the `normandy` API here: https://xor.cat/assets/other/random/2019-05-04/normandy_sign... hotfix-update-xpi-signing-intermediate-bug-1548973: https://storage.googleapis.com/moz-fx-normandy-prod-addons/e... From the looks, it installs the above plugin, and changes `app.update.lastUpdateTime.xpi-signature-verification` to `1556945257` I can't get it to work in ESR 60 though. Getting file not found on…

Hey, if you just click on that storage.googleapis.com link it installs the hotfix directly without having to enable normandy ;)

Unrelated to cert problem: Yes, clicking on the link installs the plugin, but it is suprising to see that firefox claims that it is the news.ycombinator.com, not storage.googleapis.com, that wants to install plugin. Could it be a security issue since if an attacker somehow manages the post/inject a link for a malicious plugin in a credible site, firefox will claim that plugin is from that site?

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

#787
post #470
post #461

Earlier quoted context omitted.

NoScript and uBlock Origin have stopped working. This opens up a LOT of attack surface for malicious hackers. If this isn't a critical security issue, what is?

The Container extension is no longer working. I'm logged out of mostly everything. There are few sites I don't want to open without container.

Update - Container data is lost post addons recovery (I installed Nightly build). This is ridiculous.

My Firefox usage will be so unproductive for few days. I had around 6-8 containers for different purpose, and somehow I'm habitual to using shortcut to launch a container and open whatever I'm supposed to (e.g I've access to 3 different AWS account, and I tend to press shortcut key to launch the relevant container tab)

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

#788
post #693

Earlier quoted context omitted.

I too use Debian's Firefox ESR. I noticed the "Allow Firefox to install and run studies" option in Privacy & Security Preferences a long time ago. It was unchecked and greyed out (i.e., unclickable), and a label below it says "Data reporting is disabled for this build configuration", so I gave it no further thought. This morning I woke up and launched Firefox, noticed this headline, and then noticed my extensions wer…

> noticed my extensions were still running. Reportedly, Firefox only checks the date once per day, so if it hasn’t yet checked for you today, this will be the result. > I looked in about:config and lo and behold, app.normandy.enabled=default [true]. I would assume that the config setting only has any effect if the feature is available in the build. Which it isn’t in Debian.

that would be good news, how can I verify that the Normandy feature isn't available in the Debian build?

Has Mozilla provided instructions to manually fix the issue? if so where? (XORcat was helpful to provide a solution, but I refuse to apply it if it doesn't come from Mozilla itself...)

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

#789

Earlier quoted context omitted.

I have spent ~10 years using Firefox daily, tweaking the config and getting the addons set up the way I want. I was a professional web developer for most of those years. This is the first I have heard of Firefox changing my config settings invisibly in the background. This is obscene. Who on earth thought this was a good idea? The security ramifications are limitless. I understand all too well that most companies hav…

The way that Firefox needs 5-10 privacy extensions to be usable isn't just inconvenient when the certs fail, but you also have to trust all these strangers and their extension code. I've been using brave because of that: all of that is baked in so my only extension is my password manager

So why do you use a browser made by an ad company, that is all about analysing your browser history and targetting ads at you?

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

#790
post #592

Earlier quoted context omitted.

JSON response from the `normandy` API here: https://xor.cat/assets/other/random/2019-05-04/normandy_sign... hotfix-update-xpi-signing-intermediate-bug-1548973: https://storage.googleapis.com/moz-fx-normandy-prod-addons/e... From the looks, it installs the above plugin, and changes `app.update.lastUpdateTime.xpi-signature-verification` to `1556945257` I can't get it to work in ESR 60 though. Getting file not found on…

So not only does this 'normandy' thing exist, but it goes to a google server? So much for using Firefox to keep google out of my life. :(

that's an interesting question: when we install add-ons or extensions, are these hosted on google servers? I'd rather not have google know what versions of which add-ons I am running...
Post reply on HN