Този сайт ще има ограничена функционалност, докато се извършва тече неговата поддръжка. Ако дадена статия не може реши проблема ви и искате да зададете въпрос, нашата общност е готова да ви помогне на @firefox в Twitter и /r/firefox в Reddit.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Add-ons signature

  • 2 отговора
  • 4 имат този проблем
  • 1 изглед
  • Последен отговор от 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.

Избрано решение

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/

Прочетете този отговор в контекста 👍 2

Всички отговори (2)

more options

Избрано решение

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/

more options

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