7144f8b7f8
More minor tweaks to come. This isn't final - 0102: ambiguous that the clearing was related to PB mode - 0900s: - get rid of 0901, it has no pref, stick link in header - 0905: values on multi-lines use spaces = more readable - 1000s: - rename as disk avoidance and remove sub-section headers - remove the outdated section header - 4001: it will never be perfected, it's doing it's job - 5500s: optional hardening - legit security measures, but commonality in caveats, so I made them a separate section - this flips graphite, asm.js and wasm from active to inactive: these are overkill: exhibit A: hundreds of millions of Firefox users - e.g. graphite and wasm are enabled on Tor Browser - new CVE keyword links - 7000s: don't bother - two more items added - 5000s: optional opsec and cleanout 0800s header - re-number - 0900s, 1000s, 1400s, 2400s PS: I need a new parrot: "9000 syntax error: I ran out of parrots"
🟪 user.js
A user.js is a configuration file that can control hundreds of Firefox settings. For a more technical breakdown and explanation, you can read more on the overview wiki page.
🟩 the arkenfox user.js
The arkenfox user.js is a template which aims to provide as much privacy and enhanced security as possible, and to reduce tracking and fingerprinting as much as possible - while minimizing any loss of functionality and breakage (but it will happen).
Everyone, experts included, should at least read the implementation wiki page, as it contains important information regarding a few user.js settings.
Note that we do not recommend connecting over Tor on Firefox. Use the Tor Browser if your threat model calls for it, or for accessing hidden services.
Also be aware that the arkenfox user.js is made specifically for desktop Firefox. Using it as-is in other Gecko-based browsers can be counterproductive, especially in the Tor Browser.
🟧 sitemap
🟥 acknowledgments
Literally thousands of sources, references and suggestions. Many thanks, and much appreciated.