Windows 10 bereikte EO (einde ondersteuning) op 14 oktober 2025. Als je Windows 10 gebruikt, lees dan dit artikel.

Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info
Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.
Opgelost Gearchiveerd

Add-ons signature

fergago beantwoord
fergago

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.

Alle antwoorden (2)

Gekozen 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/

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