What's Going on with Firefox Addons/Extensions?

YesItsMe · 05-11-2019, 04:23 PM

"xpinstall.signatures.required" is not doing anything in standard Firefox versions. It requires a nightly or beta version. If your distribution has a working "xpinstall.signatures.required" in a standard Firefox version, it is a bug and should be fixed.

hydrurga · 05-11-2019, 04:27 PM

Quote:

Originally Posted by cynwulf

It does:

xpinstall.signatures.required

However it is in the "about:config" hidden configuration, rather than accessible via the browser "chrome" configuration. I for one don't regard this one as "easy-to-access" - it's perhaps easier than editing prefs.js / user.js directly, but that's about it.

But when all is said and done the signed add ons is a good thing, e.g. like signed packages for a given Linux distribution.

As far as I am aware, setting xpinstall.signatures.required to false only actually works on developer and nightly versions of Firefox, and some Linux distros. Here for example - https://superuser.com/questions/1432...re-enable-them :

Quote:

Setting xpinstall.signatures.required to false will not work on the Beta or Release versions of Firefox on Mac or Windows. Doing so has no effect. On Linux, depending on your distribution, the setting may be respected and does work on some distributions of the release version of Firefox.

scasey · 05-11-2019, 04:31 PM

From https://support.mozilla.org/en-US/kb...ing-in-firefox

Quote:

Firefox Extended Support Release (ESR), Firefox Developer Edition and Nightly versions of Firefox will allow you to override the setting to enforce the extension signing requirement, by changing the preference xpinstall.signatures.required to false

The distro supplied version on CentOS is an ESR

cynwulf · 05-11-2019, 04:57 PM

Quote:

Originally Posted by YesItsMe

"xpinstall.signatures.required" is not doing anything in standard Firefox versions. It requires a nightly or beta version. If your distribution has a working "xpinstall.signatures.required" in a standard Firefox version, it is a bug and should be fixed.

Quote:

Originally Posted by hydrurga

As far as I am aware, setting xpinstall.signatures.required to false only actually works on developer and nightly versions of Firefox, and some Linux distros. Here for example - https://superuser.com/questions/1432...re-enable-them :

Ok fair enough, I wasn't aware of that.

I am using the OpenBSD port of firefox 62.0.3. It certainly works here.

//edit: also reported to work in 66.0.3 in 6.5-release ports.

https://marc.info/?l=openbsd-misc&m=155699684723929&w=2

(Fixed version 66.0.4 uploaded to the port maintainer's own repository.)

mark_alfred · 05-11-2019, 06:53 PM

Tor Browser released an update. So the NoScript addon works now, and the temporary fix as described here can be undone.

grumpyskeptic · 05-13-2019, 02:46 PM

When I opened Firefox 66.0.3 a couple of minutes ago, I found that 100% of my add-ons have been deactivated, all of them saying "...could not be verified for use in Firefox and has been disabled". This is even worse that when it happened the first time, when two or three still worked.

Has anyone else experienced this again?

I had a problem with the computer clock being years out of date when I started Firefox, might that be connected to the problem? I have now corrected the clock time, the add-ons are still deactivated.

Edit - suddenly everything has returned to normal, all add-ons now working.

scasey · 05-13-2019, 02:50 PM

Quote:

Originally Posted by grumpyskeptic

When I opened Firefox 66.0.3 a couple of minutes ago, I found that 100% of my add-ons have been deactivated, all of them saying "...could not be verified for use in Firefox and has been disabled". This is even worse that when it happened the first time, when two or three still worked.

Has anyone else experienced this again?

I had a problem with the computer clock being years out of date when I started Firefox, might that be connected to the problem? I have now corrected the clock time, the add-ons are still deactivated.

Edit - suddenly everything has returned to normal, all add-ons now working.

FYI, the latest, "fixed" version of Firefox Quantum is 66.0.5

kingbeowulf · 05-13-2019, 08:35 PM

Firefox 60.6.3ESR, the latest patches backported to ESR fixes the last of the extension glitches, for Slackware-14.2 (Stable). I was not aware of this master password bug. All is good now here with ABP, Noscript, Duckduckgo privacy, user agent switcher.

Quote:

hu May 9 01:39:14 UTC 2019
patches/packages/mozilla-firefox-60.6.3esr-x86_64-1_slack14.2.txz: Upgraded.
This update provides further improvements to re-enable web extensions which
had been disabled for users with a master password set (Bug 1549249).
For more information, see:
https://www.mozilla.org/en-US/firefo.../releasenotes/
+--------------------------+
Mon May 6 01:29:24 UTC 2019
patches/packages/mozilla-firefox-60.6.2esr-x86_64-1_slack14.2.txz: Upgraded.
This update addresses the issue of add-ons failing to load.
For more information, see:
https://www.mozilla.org/en-US/firefo.../releasenotes/

carlito386 · 05-16-2019, 04:22 PM

Quote:

Originally Posted by kingbeowulf

Firefox 60.6.3ESR, the latest patches backported to ESR fixes the last of the extension glitches, for Slackware-14.2 (Stable). I was not aware of this master password bug. All is good now here with ABP, Noscript, Duckduckgo privacy, user agent switcher.

DDG? There's also Startpage and Searx search engines.
They even offer a proxy service to view sites anonymously.
There is Qwant too - but I'm not sure what to make of it.