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

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Changing the default channel-prefs.js

  • 1 baphendule
  • 1 inale nkinga
  • 5 views
  • Igcine ukuphendulwa ngu cor-el

more options

Hi,

i have been given task to change config for Mozilla ESR users in our company. I'm trying to change the value "security.enterprise_roots.enabled" which is disabled by default in update channel "esr". Is it safe to push (mass copy) new file "channel-prefs.js" with modified preference or there is another way?

pref("app.update.channel", "esr"); /* extra code */ pref("security.enterprise_roots.enabled", true);

Hi, i have been given task to change config for Mozilla ESR users in our company. I'm trying to change the value "security.enterprise_roots.enabled" which is disabled by default in update channel "esr". Is it safe to push (mass copy) new file "channel-prefs.js" with modified preference or there is another way? pref("app.update.channel", "esr"); /* extra code */ pref("security.enterprise_roots.enabled", true);

All Replies (1)

more options

No you shouldn't modify this file, but instead use a mozilla.cfg file in the main Firefox program folder.

You can use the mozilla.cfg file in the Firefox program folder to set or lock preferences and run privileged JavaScript code.

The mozilla.cfg file needs to be in the main Firefox program folder.

These functions can be used in the mozilla.cfg file:

defaultPref();	// set new default value
pref();	// set pref, allow changes in current session
lockPref();	// lock pref, disallow changes

This requires a local-settings.js file in the "defaults/pref" folder where the channel-prefs.js file is located that specifies to use mozilla.cfg.

//
pref("general.config.filename", "mozilla.cfg");
pref("general.config.obscure_value", 0);

The mozilla.cfg and local-settings.js files need to start with a comment line (//).

See Configuration:

See also: