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.

Issues locking down a system with local-settings.js

  • 3 uphendule
  • 4 zinale nkinga
  • 243 views
  • Igcine ukuphendulwa ngu tbertschi

more options

I need a sanity check.

I'm trying to lock down Firefox in Windows and Linux. I'm following the instructions to create local-settings.js and mozilla.cfg files. Right now, I'm working on just changing the default webpage. I'll screw things up later once I get past this hurdle. I'm currently working on a 2012 Server but I'm pretty sure I can replicate the issue on my RH 6 box.

The issue is when I create these 2 files and put them in the defaults/pref directory (which is what is referenced in my security paper and research on the intarwebs) it doesn't work. But if I copy the files to the install directory for Firefox, they do. Normally, this would be fine but this deviates from the security paper I have to follow to check the contents of the file and I don't want to have to explain the issue or get dinged. Are the locations correct or do I need to keep them in the defaults/pref and if I do, why do the same files error in one directory but not in another?

Thank you for your assistance. Peace

local-settings.js


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

I need a sanity check. I'm trying to lock down Firefox in Windows and Linux. I'm following the instructions to create local-settings.js and mozilla.cfg files. Right now, I'm working on just changing the default webpage. I'll screw things up later once I get past this hurdle. I'm currently working on a 2012 Server but I'm pretty sure I can replicate the issue on my RH 6 box. The issue is when I create these 2 files and put them in the defaults/pref directory (which is what is referenced in my security paper and research on the intarwebs) it doesn't work. But if I copy the files to the install directory for Firefox, they do. Normally, this would be fine but this deviates from the security paper I have to follow to check the contents of the file and I don't want to have to explain the issue or get dinged. Are the locations correct or do I need to keep them in the defaults/pref and if I do, why do the same files error in one directory but not in another? Thank you for your assistance. Peace local-settings.js ---------------------------------- // Filler comment pref("general.config.filename", "mozilla.cfg"); pref("general.config.obscure_value", 0);

Isisombululo esikhethiwe

Only local-settings.js needs to be in the "defaults/pref" folder. The mozilla.cfg needs to be placed in the main Firefox installation folder.

A local-settings.js file needs to be placed in the "defaults/pref" folder where also the channel-prefs.js file is located to specify using mozilla.cfg.

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

The mozilla.cfg file needs to start with a comment line (//) since this line will be skipped.

See Configuration:

Funda le mpendulo ngokuhambisana nalesi sihloko 👍 1

All Replies (3)

more options

Yes, mozilla.cfg and *.js files should be placed in the install directory (where the firefox.exe is placed).

more options

Isisombululo Esikhethiwe

Only local-settings.js needs to be in the "defaults/pref" folder. The mozilla.cfg needs to be placed in the main Firefox installation folder.

A local-settings.js file needs to be placed in the "defaults/pref" folder where also the channel-prefs.js file is located to specify using mozilla.cfg.

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

The mozilla.cfg file needs to start with a comment line (//) since this line will be skipped.

See Configuration:

more options

Thanks guys. Getting a definitive answer helps a lot. Now to just tweak my check scripts to know what's in the mozilla.cfg file.