Firefox ver. 43 update disabling NoScript, add-on unsigned

schpoink · Post by **schpoink** » Thu Dec 17, 2015 1:49 pm

What gives?

I updated my version of Firefox (Windows) this morning to version 43, and it has disabled the NoScript extension because it is not signed.

Is this something you are planning to do (soon!)?

Post by **therube** » Thu Dec 17, 2015 2:36 pm

NoScript is signed.
The question is why does it show otherwise - in particular Profiles?
(And I haven't figured that one out myself.)

Signing: could not be verified for use in Firefox.

Now, in a different Profile, it should work, if you wanted to go that route.
Or... ?

Post by **barbaz** » Thu Dec 17, 2015 9:42 pm

Where are you installing NS from? Official sources are AMO or https://noscript.net/. If you haven't installed from AMO (which you have if installed through the Add-ons Manager interface for finding other addons), does installing from AMO change the situation?

Post by **therube** » Thu Dec 17, 2015 9:59 pm

(Both from AMO & from here [not the case with FlashGot, last time I checked] are signed.)

Post by **Thrawn** » Thu Dec 17, 2015 11:01 pm

Also - what version of NoScript are you running? Maybe it's outdated?

Post by **therube** » Fri Dec 18, 2015 1:02 am

See, viewtopic.php?p=80494#p80494.

Oops, do note, that doing what I've described will affect ALL extensions.
Backup first.
I only looked at it from the perspective of the particular issue with NoScript, alone, showing as unsigned.

InformAction Forums

Firefox ver. 43 update disabling NoScript, add-on unsigned

Firefox ver. 43 update disabling NoScript, add-on unsigned

Re: Firefox ver. 43 update disabling NoScript, add-on unsign

Re: Firefox ver. 43 update disabling NoScript, add-on unsign

Re: Firefox ver. 43 update disabling NoScript, add-on unsign

Re: Firefox ver. 43 update disabling NoScript, add-on unsign

Re: Firefox ver. 43 update disabling NoScript, add-on unsign