We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Add-ons signature

  • 2 antwurd
  • 4 hawwe dit probleem
  • 1 werjefte
  • Lêste antwurd fan 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.

Keazen oplossing

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/

Dit antwurd yn kontekst lêze 👍 2

Alle antwurden (2)

philipp
philipp
  • Moderator
more options

Keazen oplossing

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 Fraacheigener
more options

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