To find out what other preferences you can set in this file, all you have to do is open up the about:config page. The configuration option for this would be: Let’s say, for example, we want to set the default homepage to the TechRepublic site. To lock a preference in about:config, a line will start with lockPref. The next lines in the file will contain all of the configuration options. The first line of this file is always ignored, so we’re going to simply add an empty comment, like so: Within that file we’re going to lock down the about:config preferences we don’t want the users to be able to change. The first thing we must do is create a new file called mozilla.cfg. Change into that folder with the command cd firefox. You should now see a folder named firefox. Let’s move that out of the parent folder with the following commands:Ĭd firefox-XX (where XX is the release number) Within that folder is the sub-folder, firefox. This will create a new folder called firefox-XX (where XX is the release number). Unpack the file with the command tar xvfj firefox-*.bz2. Open up your terminal and change into the ~/Downloads directory with the command cd ~/Downloads. The first thing we must do is unpack the downloaded file. Once you have everything ready, let’s get to work. Download the latest version of Firefox into the ~/Downloads directory. You will also need to use the terminal window.
#Force enable java in firefox download#
You will need to download the latest version of Firefox from Mozilla and uninstall the version of Firefox that was included either via the default operating system installation or from with the OS package manager.
#Force enable java in firefox windows#
The process is similar on both Windows and macOS, although the specifics on file locations will vary. I’ll demonstrate on the Linux platform (using Ubuntu 17.10 and Firefox 59). I’m going to walk you through the process of doing just that. Even though completely disabling about:config isn’t really an option, you can always lock down certain settings within about:config, and then deploy that newly configured browser. Since the release of Firefox Quantum, have you made the change to Firefox in your company? If that’s the case, are you concerned about users making changes to the browser that might go against company policy, or pose security risks? Although the average user might not know the about:config feature exists, there will be some that do. Jack Wallen walks you through the process of locking down options with Firefox's about:config page to help secure the browser from user tampering. How to deploy Firefox with locked about:config settings