InformAction Forums

Just updated my Firefox 40.0b9 build 1 win64 beta to 41.0b1 build 1 win64 beta; however, I noticed that 3 of my Add-ons Extension (FoxClocks, Https-Everywhere, and NoScript 2.6.9.35 final version) were all disabled. I was able to enable FoxClocks extension by adding its corresponding links to Exceptions (and allow and save the changes) under Options, Security, General-Warn me when sites try to install add-ons. Then tried re-installing it and works. I did the same thing to the remaining Add-ons Extensions, including NoScript, but it did not work. By the way, I am using Windows 10 Pro 64-bit OS. Is there any work-around in installing and enabling NoScript 2.6.9.35 final version? - Thanks.

Is your NS installed from AMO?

So whats the deal?


Is it supposed to be FF 41 where the crap hits?
And with that Release versions (FF 41 Release) & Beta (which FF 41b1 is now?) won't allow overrides?

https://foxclocks.org/ links to AMO, so it should work.

https://www.eff.org/Https-Everywhere self-hosts versions, so if you got it directly from them, then it should not be working.

Likewise with NoScript, the version hosted on noscript.net will not work with FF 41, but the version from AMO will.

You need to get it from AMO.

I was able to enable FoxClocks extension by adding its corresponding links to Exceptions

No, thinking it worked not because you added their domain as an allowable install sites, but because the extension came from AMO & is signed there.


(What a PITA this is, & will be even more so, shortly.)

(@barbaz, & BTW, appears that when building, signing will go opt-out, so you'll need to set some variable [or something or the other] in your [SeaMonkey/TB] build scripts to avoid signing requirement - or something to that effect, if I'm understanding correctly.)

therube wrote:(@barbaz, & BTW, appears that when building, signing will go opt-out, so you'll need to set some variable [or something or the other] in your [SeaMonkey/TB] build scripts to avoid signing requirement - or something to that effect, if I'm understanding correctly.)

Thanks for the info, I'm aware of this (one of the participants of that bug was so kind to CC me).

(Now that you mention it, I remember seeing your name on the CC: list. Duh!)

BTW, this may help: http://www.ghacks.net/2015/08/04/fix-fo ... d-nightly/

@barbaz & @therube:

Many thanks! Now NoScript 2.6.9.35 final version works and enabled by going to the AMO links, but "HTTPS-Everywhere" seems like still unsigned and could not install (disabled). Thank you for pointing out how to, unlike what I usually do as to just clicking on "Check on updates" on "Add-ons" which works prior to Firefox 41.0b1 build 1 beta win64.

> this may help: http://www.ghacks.net/...

But that deals with extensions "in Firefox Dev and Nightly" & (theoretically) there shouldn't be any issues there, as overrides are available.

But (I'm supposing) the OP's 41.0b1 is now treated as Beta, & Release & Beta won't have such mechanisms.


> HTTPS-Everywhere" seems like still unsigned and could not install

Again the version direct from eff.org won't work, you have to get it from AMO: HTTPS Everywhere 5.0.7.

Seems that with FF 41 Beta/Release (but nothing later), you can set the Pref: xpinstall.signatures.required to 'false' & that will allow any extension to install.

(Again, will not work in FF 42+.)


Wiki: Addons/Extension Signing