Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

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

Ova tema je arhivirana. Pitajte drugo pitanje ako vam je potrebna pomoć.

Add-ons signature

  • 2 odgovori
  • 4 ima ovaj problem
  • 1 view
  • Posljednji odgovor poslao 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.

Izabrano rješenje

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/

Pročitajte ovaj odgovor sa objašnjenjem 👍 2

All Replies (2)

philipp
philipp
  • Moderator
more options

Odabrano rješenje

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 Vlasnik pitanja
more options

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