Turning off Mozilla AutoUpdate

From ASU HOWTO
Revision as of 14:54, 26 February 2020 by Woodisdd ws (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Content pulled from : http://kb.mozillazine.org/Locking_preferences

Guide

[edit] Determining settings You must first determine which settings you want to lock. This can be done multiple ways: A mostly complete list describing available settings can be found online on the about:config entries page. Preference settings, both user-specified and default values, are displayed in the about:config window while Firefox or Mozilla Suite is running. Settings shown here are updated as you change them in the browser. When the browser closes, it saves user-specified settings to the prefs.js file in the profile folder. If all else fails, you can ask in the forums or on IRC. Since it is commonly requested, we will use the browser proxy setting as an example. If you search for "proxy", you will eventually find the preference string for this option is "network.proxy.type". As described in the about:config entries article, the setting to use a direct connection is 0. [edit] Creating the lock file Next, create a text file, and make the first line start with double forward slashes. On the next line(s), add the preferences you want to lock. The format of these lines is similar to that found in prefs.js, except that lockPref is used instead:

//
lockPref("network.proxy.type", 0);

Save the file as mozilla.cfg in your your installation directory (where the seamonkey, thunderbird or firefox executable is located) Note: This document (like many references throughout the web) previously recommended encoding this file as ROT13. This requirement is not mandatory and can easily be circumvented when loading the lock file (see below). [edit] Loading the lock file Finally, you must tell the application to load the lock file. Create a new file (eg "local-settings.js") in the defaults/pref subfolder of the installation directory. Open the "local-settings.js" file in a text editor and add the following line to the bottom, which points to the newly created lock file.

pref("general.config.obscure_value", 0); // only needed if you do not want to obscure the content with ROT-13
pref("general.config.filename", "mozilla.cfg");

Save the change and completely restart Firefox. Now, all of the prefs listed will be locked. Notes: This document previously recommended modifying the "all.js" file in the greprefs subfolder. Doing so breaks application updates whenever all.js must be updated, more details are given in bug 448504. Furthermore (see below) in current versions the greprefs subfolder does not exist anymore, and greprefs/all.js has been renamed greprefs.js. In current versions of Firefox, Thunderbird and SeaMonkey, the file greprefs.js and the defaults/pref directory are part of the zipfile omni.jar found at top level of the installation directory. You can still place the file local-settings.js in the defaults/pref folder where also the channel-prefs.js file is located [1]. [edit] Optional Steps

[edit] Hiding options Since these settings can no longer be changed by the user, you may want to prevent them from being shown at all in the GUI. This purely cosmetic change can be done by modifying userChrome.css. [edit] Restricting file access A user who can modify local-settings.js can obviously remove the lock file reference and change those settings. Revoking write authority from the user for local-settings.js would prevent this. However, it should be noted that doing this may prevent the user from upgrading Firefox in the future, as new major versions may contain changes to related files (such as "all.js"). [edit] Caveats Since it is possible to completely bypass locked preferences by running a separate version of Firefox or Mozilla Suite (or a completely different browser) from a different location, it may be necessary to restrict which programs can be run. However, at this point, it is probably a good idea to examine exactly why you are locking the preferences in the first place. If the intent is to protect users from themselves, or to keep novice users from breaking their software, then you have probably done enough. However, if you are trying to secure your network using client-side settings, then you should realize this is very difficult, and ultimately wastes too many resources. Instead, you should probably redirect your efforts to the server/router where you can fight battles that are more easily won. [edit] Undoing To unlock all preferences, remove the entry you added earlier from the "local-settings.js" file and completely restart Firefox or Mozilla Suite.