All extensions disabled due to expiration of intermediate signing cert • Hacker News Board

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

#831

Post by hrbf » Sat, May 04, 2019, 6:55 PM UTC

gpm wrote: post #728

igivanov wrote: post #724

Earlier quoted context omitted.

TypeError: Components.utils is undefined[Learn More] what did I do wrong? (It's all Greek to me)

What version of firefox are you running? Apparently beta and nightly need to change `Components.utils.import` to `ChromeUtils.import`. But anyways, don't use this now, use the semi-official fix of clicking on this link and letting it install: https://storage.googleapis.com/moz-fx-normandy-prod-addons/e... This is the fix Mozilla has published to be installed via shield studies, but skipping the shield studies part. Y…

Confirmed working with 66.0.3 (64-bit) on macOS 10.14.4 (18E226). After installation all plugins immediately came back.

This should really be one of the official ways to apply the patch instead of only telling users "it can take up to 6 hours for the fix to be installed" after enabling Shield studies. I can only imagine what kind of havoc this creates in businesses using Firefox working weekends.

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

#832

Post by gpm » Sat, May 04, 2019, 7:03 PM UTC

arrivance wrote: post #830

gpm wrote: post #812

Earlier quoted context omitted.

Not sure what would be causing a connection failure. I just verified that the link is still up for me, and obviously you have an internet connection if you're replying to me. You're not behind a firewall that might be blocking it are you? E.g. being in China?

I can report a connection failure while being on a unrestricted connection (University internet in the UK).

So, I don't have any good ideas why. Can you give me more information about what exactly happens? Can't promise anything but details might help.

I.e. something like

- I open the browser console

- I click the .xpi link

- The following appears in the browser console immediately after clicking the link:

    WebExtensions: new intermediate certificate added api.js:15
    WebExtensions: signatures re-verified api.js:23

- My addons do not come back

- If I try to install an addon from addons.mozilla.org I get in the browser console.

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

#833

Post by masterfooo » Sat, May 04, 2019, 7:03 PM UTC

After learning about Normady thing, I am literally now blocking every Mozilla, Firefox and their affiliate domains and their Ip adresses. The trust is lost. I rely on Debian repo and like other's mentioned, Normandy seems to bypass Debian oversight.

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

#834

Post by ipatmos » Sat, May 04, 2019, 7:04 PM UTC

gpm wrote: post #828

ipatmos wrote: post #782

Earlier quoted context omitted.

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?

No, the mozilla fix should have wiped out everything this did. Edit: I.e. you're good to go.

thank you so much for your help!!

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

#835

Post by ContrQ » Sat, May 04, 2019, 7:07 PM UTC

gpm wrote: post #728

igivanov wrote: post #724

Earlier quoted context omitted.

TypeError: Components.utils is undefined[Learn More] what did I do wrong? (It's all Greek to me)

What version of firefox are you running? Apparently beta and nightly need to change `Components.utils.import` to `ChromeUtils.import`. But anyways, don't use this now, use the semi-official fix of clicking on this link and letting it install: https://storage.googleapis.com/moz-fx-normandy-prod-addons/e... This is the fix Mozilla has published to be installed via shield studies, but skipping the shield studies part. Y…

Applying the fix via the link above, will anything need to be done after this is all resolved. Example will this fix need removed or any settings it may edit be restored in about:config?

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

#836

Post by DamienBourg » Sat, May 04, 2019, 7:18 PM UTC

gpm wrote: post #728

igivanov wrote: post #724

Earlier quoted context omitted.

TypeError: Components.utils is undefined[Learn More] what did I do wrong? (It's all Greek to me)

What version of firefox are you running? Apparently beta and nightly need to change `Components.utils.import` to `ChromeUtils.import`. But anyways, don't use this now, use the semi-official fix of clicking on this link and letting it install: https://storage.googleapis.com/moz-fx-normandy-prod-addons/e... This is the fix Mozilla has published to be installed via shield studies, but skipping the shield studies part. Y…

Thks, it worked, I installed the fix. But do I have to uninstall the .xpi after? And how? Also, my addons are back, but I still have the error message (see screenshot: http://i.imgur.com/t1wb316.png ) Also do I still have to allow the "allow firefow to install and run studies"? Thks.

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

#837

Post by rue » Sat, May 04, 2019, 7:22 PM UTC

Yoric wrote: post #566

nanis wrote: post #559

Earlier quoted context omitted.

>> Is the existence of a back door method of updating Firefox preferences something that will be disclosed to users? > It will even be documented for them: That sounds like you do not think the concern is warranted. I've used Firefox since the first time it was available, and Netscape starting with the first ever betas. At no point was there a dialog that said "Do you want us to be able to change your browser setting…

> So, the question can be rephrased as "is the fact that Firefox has been logging all users' entire browsing history despite the fact that the user has not chosen to set up a Firefox account going to be disclosed?" Chill out, this preference only determines what is logged locally (never sent to the server). It's a debugging tool. Sources: - https://searchfox.org/mozilla-central/source/toolkit/compone... - https://sea…

Look, at this point it’s not the user’s responsibility to “chill out”. It’s very much Firefox’s responsibility to try to repair their reputation by:

1. being completely transparent about all the mechanisms that data or code can be pushed to or pulled by the browser, or pushed from or pulled from the browser; and

2. having a toggle for all of them, yes every single one, in Privacy & Security.

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

#838

Post by gpm » Sat, May 04, 2019, 7:22 PM UTC

DamienBourg wrote: post #836

gpm wrote: post #728

Earlier quoted context omitted.

What version of firefox are you running? Apparently beta and nightly need to change `Components.utils.import` to `ChromeUtils.import`. But anyways, don't use this now, use the semi-official fix of clicking on this link and letting it install: https://storage.googleapis.com/moz-fx-normandy-prod-addons/e... This is the fix Mozilla has published to be installed via shield studies, but skipping the shield studies part. Y…

Thks, it worked, I installed the fix. But do I have to uninstall the .xpi after? And how? Also, my addons are back, but I still have the error message (see screenshot: http://i.imgur.com/t1wb316.png ) Also do I still have to allow the "allow firefow to install and run studies"? Thks.

I don't see any reason that you need to uninstall the .xpi, but you might as well. See here (hoping someone replies there with a better method of uninstalling, my method is a bad hack) https://news.ycombinator.com/item?id=19827428

You don't need to allow firefox to install and run studies, that's just a way of letting firefox automatically install this xpi.

Did that error message only appear after you installed the .xpi fix? If so it's mildly worrisome, but probably not worth spending time figuring out what it's about if all your addons are back. If it appeared when the addons were initially disabled it's not an issue at all, it's just that nothing closed it.

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

#839

Post by arrivance » Sat, May 04, 2019, 7:22 PM UTC

gpm wrote: post #832

arrivance wrote: post #830

Earlier quoted context omitted.

I can report a connection failure while being on a unrestricted connection (University internet in the UK).

So, I don't have any good ideas why. Can you give me more information about what exactly happens? Can't promise anything but details might help. I.e. something like - I open the browser console - I click the .xpi link - The following appears in the browser console immediately after clicking the link: WebExtensions: new intermediate certificate added api.js:15 WebExtensions: signatures re-verified api.js:23 - My addon…

Thanks for the response!

So,

I click the link. I click "Add", and Mozilla says addon could not be downloaded due to connection failure. Nothing appears in browser console.

Downloading an addon gives me "Download failed. Please check your connection." on the Addons site. In console, I get:

  Events to handle the installation initialized. BigInteger.js:27
  [GA: OFF] sendEvent {"hitType":"event","eventCategory":"AMO Addon Installs Download Failed","eventAction":"addon","eventLabel":"uBlock Origin"} BigInteger.js:27
  Error:

In the studies, I have https://i.imgur.com/fqrd5Jo.png. I enabled it, and have tried setting both first run, and the update interval is set to 21 (to try and force it to update it quickly).

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

#840

Post by gpm » Sat, May 04, 2019, 7:25 PM UTC

ContrQ wrote: post #835

gpm wrote: post #728

Earlier quoted context omitted.

What version of firefox are you running? Apparently beta and nightly need to change `Components.utils.import` to `ChromeUtils.import`. But anyways, don't use this now, use the semi-official fix of clicking on this link and letting it install: https://storage.googleapis.com/moz-fx-normandy-prod-addons/e... This is the fix Mozilla has published to be installed via shield studies, but skipping the shield studies part. Y…

Applying the fix via the link above, will anything need to be done after this is all resolved. Example will this fix need removed or any settings it may edit be restored in about:config?

Not really, you could uninstall the .xpi but it's just a matter of "cleanliness", hoping someone replies with a better method, but I replied to this comment with one way: https://news.ycombinator.com/item?id=19827428