News for hackers. Stuff that matters.
Re:Firefox Privacy How-To Guide by nominated1 on Tuesday October 15, 2019 @11:41AM (#21259638)
Many of these sites suggest making edits via “about:config”. The problem is it’s difficult to keep track of which settings you’ve altered. I highly recommend you use a user.js [1] file. The best part is you can make notes so later you knows why a setting was enabled or disabled.

The only downside is if you decide to undo a setting in user.js you’ll also have to make the same change in about:config.

[1] http://kb.mozillazine.org/User.js_file

Re:Firefox Privacy How-To Guide by cpeterso on Tuesday October 15, 2019 @01:03PM (#21260814)
Firefox's about:support page lists the about:config prefs that have non-default values ("Important Modified Preferences"). That includes prefs you've changed and internal prefs changed by Firefox code.
Re:Firefox Privacy How-To Guide by nominated1 on Tuesday October 15, 2019 @01:48PM (#21261422)
Unfortunately the info provided by about:support doesn’t separate changes made via the gui and changes made via about:config. It also includes settings that may have been altered by Add-ons.

Another benefit to using a user.js file is that your changes are persistent. If Mozilla changes a setting via an upgrade, like they did with experiments and plan to do with DoH, your changes aren’t overridden.

Re:Firefox Privacy How-To Guide by L0stLink on Wednesday October 16, 2019 @02:03AM (#21267503)
They are saved under the user profile directory in the `prefs.js` file. src[0] I have it symlinked to `~/.config/firefox/pref.js` (which also contains `chrome/userChrome.css`, also symlinked to from the firefox profile) in this way they get checked into git with the rest of my dotfiles.

[0] https://support.mozilla.org/si/questions/965842

Re:Firefox Privacy How-To Guide by dependenttypes on Tuesday October 15, 2019 @02:06PM (#21261653)
Another issue is that most of such modifications also suggest editing the allowed ciphers, which makes it easier for servers to track you.
Re:Firefox Privacy How-To Guide by leeoniya on Tuesday October 15, 2019 @12:16PM (#21260144)
Re:Firefox Privacy How-To Guide by ilikenwf on Tuesday October 15, 2019 @04:19PM (#21263257)
Re:Firefox Privacy How-To Guide by leeoniya on Tuesday October 15, 2019 @10:06PM (#21266354)
good call. looks more actively maintained.
Re:Firefox Privacy How-To Guide by ilikenwf on Friday October 18, 2019 @08:58PM (#21296175)
The maintainers and pull requesters are very persnickety too, so they usually are ahead of Mozilla's future releases.
Re:Firefox Privacy How-To Guide by george_perez on Tuesday October 15, 2019 @12:58PM (#21260729)
Modified about:config settings appear in bold, though. It's good for a quick glance, but yeah not much after that.
Re:Firefox Privacy How-To Guide by mackrevinack on Tuesday October 15, 2019 @01:37PM (#21261280)
and I remember one time being able to reorder the list so it shows all the modified items at the top
Re:Firefox Privacy How-To Guide by catalogia on Tuesday October 15, 2019 @01:38PM (#21261289)
Sorting by the "Status" column still does this.
Re:Firefox Privacy How-To Guide by johnp_ on Tuesday October 15, 2019 @07:05PM (#21264991)
As long as `chrome://global/content/config.xul` still exists, you can use it. I certainly do, since the new interface is horrible and Mozilla constantly dismisses the obvious usability issues.
Re:Firefox Privacy How-To Guide by OJFord on Wednesday October 16, 2019 @03:30AM (#21267967)
Thanks for this, I use it and userChrome for some add-on alterations, but it didn't occur to me I could use it for 'manual' about:config changes.

> The only downside is if you decide to undo a setting in user.js you’ll also have to make the same change in about:config.

You could change it to the inverse/default explicitly in user.js?