This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Add-ons signature

  • 2 replies
  • 4 have this problem
  • 1 view
  • Last reply by fergago

fergago
fergago
more options

In order to use non-secure add-ons at my own risk, a few FF versions ago I made this change in about:config xpinstall.signatures.required ...........FALSE I have just installed version 48.0 and I see that now, unverified add-ons are directly disabled without any chance to enable them back, only removing them. I assume that the about:config feature " xpinstall.signatures.required" is no longer useful, is it? Thanks.

In order to use non-secure add-ons at my own risk, a few FF versions ago I made this change in about:config xpinstall.signatures.required ...........FALSE I have just installed version 48.0 and I see that now, unverified add-ons are directly disabled without any chance to enable them back, only removing them. I assume that the about:config feature " xpinstall.signatures.required" is no longer useful, is it? Thanks.

Chosen solution

hi fergago, this preference was always intended to be used through a transitional period - starting with firefox 48 the requirement that extensions need to be signed is enforced in firefox release builds without the option to work around that. you can still use that preference in firefox developer edition though: https://www.mozilla.org/firefox/developer/

Read this answer in context 👍 2

All Replies (2)

philipp
philipp
  • Moderator
more options

Chosen Solution

hi fergago, this preference was always intended to be used through a transitional period - starting with firefox 48 the requirement that extensions need to be signed is enforced in firefox release builds without the option to work around that. you can still use that preference in firefox developer edition though: https://www.mozilla.org/firefox/developer/

fergago
fergago Question owner
more options

Thanks philipp, I assumed so. I'll stick to the "average skilled guy" FF edition :)