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

681–690 of 955 posts

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

#681

Post by taxatu »

neilv wrote: post #604
rmbryan wrote: post #520

Update: We have rolled out a partial fix for this issue. We generated a new intermediate certificate with the same name/key but an updated validity window and pushed it out to users via Normandy (this should be most users). Users who have Normandy on should see their add-ons start working over the next few hours. We are continuing to work on packaging up the new certificate for users who have Normandy disabled.

I've been through all of Firefox `about:config` a few times in the past, fixing preferences to, e.g., try to disable umpteen different services that leak info or create potential vulnerabilities gratuitously, but this is the first I recall hearing of Normandy. Apparently I missed `app.normandy.enabled`, because I think I would've remembered a name with connotations of a bloody massive surprise attack. Incidentally, `…

Can we get a clarification:

Unchecking "Allow Firefox to install and run studies" in the UI does not change "app.normandy.enabled" to "false".

Then, does unchecking "Allow Firefox to install and run studies" really disable Normandy, or not?

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

#683

Post by kisamoto »

So:

  * Started day with browser, no problems with extensions
  * At some point in the afternoon, all extensions disappeared
  * A couple of hours (cannot be more specific I am afraid), all extensions came back
However I'm noticing the saved preferences of some of the extensions has gone. e.g. Password manager has kept the username however all "Multi-account containers" are now reset to factory defaults.

Is anybody seeing similar behaviour ?

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

#684

Post by onli »

galangalalgol wrote: post #630
onli wrote: post #589

Earlier quoted context omitted.

Just FYI, that's not really true. Adblocker use mostly all the same filter lists and those do regularly block ads that just are regular images, and even text notes. https://www.troyhunt.com/ad-blockers-are-part-of-the-problem... is an example, even if that specific one got resolved Adblock Plus has the ability to not block ads that conform to a certain standard, but in addition to conform to standards ad publishers n…

If the images are hosted on the site instead of a third party the list won't matter.

Even my example I linked in the comment you answered to is not about an image hosted on a different server. It's not an image at all. And ublock origin even still blocks it today.

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

#686

Post by taneq »

bilbo0s wrote: post #650
robolange wrote: post #631

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…

I had mine disabled. So let's think about this for a second. If I disable a security hole that you can drive a semi-truck through, I remain foobar'd. If I run my "secure" firefox configuration, with the security hole enabled, then they un-foobar me first. Before anyone else. So I could effectively get rewarded, for always keeping a security hole open. But I didn't keep it open, so... yeah... they'll get around to me…

> So I could effectively get rewarded, for always keeping a security hole open.

That's the way it always works, isn't it? Security and convenience are opposing concerns.

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

#687

Post by zyrox »

Marc66FR wrote: post #644
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…

Doesn't work for me (latest FF on MacOS). I get TypeError: Componets.utils is undefined

Same here, with FFv66.0.3 on Arch. On FFv66.0.2 as well. Tried some suggestions I found on the internet, but no luck there either.

#Edit: found you need to be on about:addons, then paste the code.

Thanks!

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

#688

Post by tux3 »

kisamoto wrote: post #683

So: * Started day with browser, no problems with extensions * At some point in the afternoon, all extensions disappeared * A couple of hours (cannot be more specific I am afraid), all extensions came back However I'm noticing the saved preferences of some of the extensions has gone. e.g. Password manager has kept the username however all "Multi-account containers" are now reset to factory defaults. Is anybody seeing…

Yep, there's a bug open for that: https://bugzilla.mozilla.org/show_bug.cgi?id=1549013

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

#689

Post by vesinisa »

taxatu wrote: post #681
neilv wrote: post #604

Earlier quoted context omitted.

I've been through all of Firefox `about:config` a few times in the past, fixing preferences to, e.g., try to disable umpteen different services that leak info or create potential vulnerabilities gratuitously, but this is the first I recall hearing of Normandy. Apparently I missed `app.normandy.enabled`, because I think I would've remembered a name with connotations of a bloody massive surprise attack. Incidentally, `…

Can we get a clarification: Unchecking "Allow Firefox to install and run studies" in the UI does not change "app.normandy.enabled" to "false". Then, does unchecking "Allow Firefox to install and run studies" really disable Normandy, or not?

As explained on Normandy's wiki page, they are related but two different things:

> Preference rollout is meant for permanent changes that we are sure of. Shield is meant for testing variations and figuring out what, if anything, is the best thing to do.

https://wiki.mozilla.org/Firefox/Normandy/PreferenceRollout#...

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

#690

Post by vesinisa »

hyeonwho4 wrote: post #605
vesinisa wrote: post #598

Earlier quoted context omitted.

I sure wonder how people so suspicious of Mozilla dare use their browser .

Setting preferences really should not be shocking, given that they have the capacity to run automatic updates. I'm more surprised that they can push code without certificates.

> I'm more surprised that they can push code without certificates.

Where are you getting this from? AFAIK all Mozilla code / prefs they can push should be signed -- this very issue seems to stem from the cert used to sign AMO extensions expired.

Post reply on HN