Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

All extensions disabled due to expiration of intermediate signing cert

bugzilla.mozilla.org

Post reply on HN
Print view View original

231–240 of 955 posts

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

#231

Post by Abishek_Muthian »

revvx wrote: post #195
Abishek_Muthian wrote: post #171

Earlier quoted context omitted.

Some shared hosting like Bluehost now provide LetsEncrypt by default for all their sites with auto-renewal (But I don't recommend Bluehost shared plans for anything even closer to serious hobby due to absurd downtimes like most other shared hosting). I used manual renewal for LetsEncrypt for about 4 websites on other shared hosts & renewing them every 3 months was a pain; had to keep reminders and schedules just not…

Another option is using a Web Server/Reverse Proxy that supports Let's Encrypt automatically, like Caddy [1]. I believe Apache HTTPD has partial support [2], too. [1] https://caddyserver.com [2] https://httpd.apache.org/docs/2.4/mod/mod_md.html

Apache HTTPD looks interesting, so using which we renew LetsEncrypt cert without using certbot?

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

#232

Post by pepa65 »

gpm wrote: 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 just set xpinstall.signatures.required to True in about:config and that fixed it after a restart.

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

#235

Post by gtdawg »

Interesting coincidence, my Ubuntu 12.04 Let's Encrypt certbox-auto updated in March 2019 to a version which no longer runs on Ubuntu 12.04 without major surgery.

https://community.letsencrypt.org/t/pip-error-with-certbot-a...

I wonder if this bit Mozilla and caused this issue.

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

#236

Post by TheRealPomax »

pepa65 wrote: post #232
gpm wrote: 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 just set xpinstall.signatures.required to True in about:config and that fixed it after a restart.

but only for dev/beta/nightly. Note that this won't work for the standard version of FF.

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

#237

Post by andrewflnr »

marcosdumay wrote: post #220
Complexicate wrote: post #58

Earlier quoted context omitted.

"...how does an organization ensure the task still gets done?" With something almost stupidly simple and low-tech: checklists. (I'm reading "The Checklist Manifesto" right now, and the points it makes seem to fit perfectly with everything you mention.)

An year is enough time for everybody that knows about the checklist to leave.

Put "make sure someone else knows all this person's checklists" on the employee exit checklist.

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

#238

Post by ddtaylor »

pepa65 wrote: post #232
gpm wrote: 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 just set xpinstall.signatures.required to True in about:config and that fixed it after a restart.

AFAIK that only works for the nighty/dev versions.

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

#239

Post by gpm »

pepa65 wrote: post #232
gpm wrote: 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 just set xpinstall.signatures.required to True in about:config and that fixed it after a restart.

Curious, that shouldn't work on branded stable installs.

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

#240

Post by TheRealPomax »

Wowfunhappy wrote: post #34

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.

You can, though, on both accounts? Use the dev version of Firefox and you get the power to ignore addon certificates, and you can already self-sign your own extensions as much as you like?
Post reply on HN