Keep addon signature requirement on by default
We're setting `MOZ_REQUIRE_SIGNING=0` during build, so it's possible to set `xpinstall.signatures.required` to `false` in `about:config`, should it be desired to install unsigned addons, while still keeping signatures required by default with this change.
This commit is contained in:
parent
e718715e4a
commit
22343234cd
|
@ -84,7 +84,8 @@ lockPref("general.config.filename", "librewolf.cfg");
|
||||||
// >>>>>>>>>>>>>>>>>>>>>>>
|
// >>>>>>>>>>>>>>>>>>>>>>>
|
||||||
|
|
||||||
// Librefox Compatibility Fix
|
// Librefox Compatibility Fix
|
||||||
defaultPref("extensions.autoDisableScopes", 0);
|
// commented out, we're setting it differently later on
|
||||||
|
// defaultPref("extensions.autoDisableScopes", 0);
|
||||||
|
|
||||||
// Removing https-everywhere adding 2 librefox addons
|
// Removing https-everywhere adding 2 librefox addons
|
||||||
// keep it commented out for now, until we have more recent, properly pre-installed addons
|
// keep it commented out for now, until we have more recent, properly pre-installed addons
|
||||||
|
@ -2648,7 +2649,7 @@ lockPref("security.tls.unrestricted_rc4_fallback", false);
|
||||||
//lockPref("ui.key.menuAccessKey", 0);
|
//lockPref("ui.key.menuAccessKey", 0);
|
||||||
//lockPref("view_source.tab", false);
|
//lockPref("view_source.tab", false);
|
||||||
|
|
||||||
defaultPref("xpinstall.signatures.required", false);
|
defaultPref("xpinstall.signatures.required", true);
|
||||||
|
|
||||||
// https://www.ghacks.net/2019/05/24/firefox-69-userchrome-css-and-usercontent-css-disabled-by-default/
|
// https://www.ghacks.net/2019/05/24/firefox-69-userchrome-css-and-usercontent-css-disabled-by-default/
|
||||||
// might increase startup time, so keep it disabled, but modifiable by default
|
// might increase startup time, so keep it disabled, but modifiable by default
|
||||||
|
|
Loading…
Reference in a new issue