user.js

Firefox configuration hardening

A user.js configuration file for Mozilla Firefox designed to harden browser settings and make it more secure.

This is a default template with every possible hardening measure enforced. See the relaxed branch for a variant providing more usability

Main goals

• Limit the possibilities to track the user through web analytics.
• Harden the browser against known data disclosure or code execution vulnerabilities.
• Limit the browser from storing anything even remotely sensitive persistently.
• Make sure the browser doesn't reveal too much information to shoulder surfers.
• Harden the browser's encryption (cipher suites, protocols).
• Limit possibilities to uniquely identify the browser/device using browser fingerprinting.
• Hopefully limit the attack surface by disabling various features.
• Still be usable in daily use.

How to achieve this?

There are several parts to all this and they are:

• Downloading and installing the user.js file.
• Reading about and applying further hardening techniques.
• Optional: Modifying user.js to adapt it to your web browser usage.

---

• Download
• Installation
• What does it do?
• Further hardening
• Known problems and limitations
• FAQ
• Contributing
• Online tests
• References
• Maintenance

---

Download

Different download methods are available:

• Clone using git: git clone https://github.com/pyllyukko/user.js
• Download and extract the ZIP file containing the latest version.
• Download the latest user.js directly

Installation

Backups

Do note that these settings alter your browser behaviour quite a bit, so it is recommended to either create a completely new profile for Firefox or backup your existing profile directory before putting the user.js file in place.

To enable the Profile Manager, run Firefox with command-line arguments: firefox --no-remote -P

Single profile installation

Copy user.js in your current user profile directory, or (recommended) to a fresh, newly created Firefox profile directory.

The file should be located at:

With this installation method, if you change any of user.js settings through about:config or Firefox preferences dialogs, they will be reset to the user.js defined values after you restart Firefox. This makes sure they're always back to secure defaults when starting the browser. However this prevents persistently changing settings you don't consider appropriate. Either edit user.js directly, or use the system-wide installation method described below.

System-wide installation (all platforms)

Generate a file suitable for system-wide installation, by running make with one of the following targets:

• systemwide_user.js: (the value will be used as default value for all Firefox Profiles where it is not explicitly set, it can be changed in about:config and is kept across browser sessions)
• locked_user.js: (the value will be used as default value on Firefox profile creation, will be locked and can't be changed) in user.js or in Firefox's about:config or settings.
• debian_locked.js: Debian specific. Users are not able to override preferences. See #415.

Copy the produced file to the Firefox installation directory. The file should be located at:

Additional installation steps for Windows / OS X / Gentoo / Archlinux

Create local-settings.js in Firefox installation directory, with the following contents:

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

This file should be located at:

If mozilla.cfg still fails to load, you must add a blank comment to the top of mozilla.cfg like so:

//

Additional settings (policies)

Not all Firefox settings can be changed through user.js - some must be set in a separate policies.json file [1]. These policies apply system-wide.

To install policies.json from this repository, simply copy it to the appropriate directory (create it if it does not exist):

Note that JSON does not support comments, hence settings are documented in custom *_comment keys. Mozilla maintains a list of available policies: [1] [2](https://github.com/mozilla/policy-templates). The Enterprise Policy Generator add-on can be used to generate policies.json files from a graphical interface.

Updating using git

For any of the above methods, you can keep your browser's user.js with the latest version available here: Clone the repository, and create a symbolic link from the appropriate location to the user.js file in the repository. Just run git pull in the repository when you want to update, then restart Firefox:

cd ~/.mozilla/firefox
git clone 'https://github.com/pyllyukko/user.js.git'
cd XXXXXXXX.your_profile_name
ln -s ${HOME}/.mozilla/firefox/user.js/user.js user.js

Verifying

Verify that the settings are effective from about:support (check the "Important Modified Preferences" and "user.js Preferences" sections).

Verify that policies are effective from about:policies.

---

What does it do?

There's a whole lot of settings that this modifies and they are divided in the following sections.

Some of the settings in this user.js file might seem redundant, as some of them are already set to the same values by default. We chose to explicitely set their values, which ensures these settings are enforced if a future Firefox update changes the default value.

HTML5 / APIs / DOM

HTML5 / APIs / DOM related settings. Mozilla is keen to implement every new HTML5 feature, which have had unforeseen security or privacy implications. This section disables many of those new and yet to be proven technologies.

• Disable Service Workers [ 1 2 3 ]
• Disable web notifications [ 1 ]
• Disable DOM timing API [ 1 2 ]
• Disable resource timing API [ 1 ]
• Make sure the User Timing API does not provide a new high resolution timestamp [ 1 2 ]
• Disable Web Audio API [ 1 ]
• Disable Location-Aware Browsing (geolocation) [ 1 ]
• When geolocation is enabled, use Mozilla geolocation service instead of Google [ 1 ]
• When geolocation is enabled, don't log geolocation requests to the console
• Disable raw TCP socket support (mozTCPSocket) [ 1 2 3 ]
• Disable leaking network/browser connection information via Javascript
• Disable network API (Firefox < 32) [ 1 2 ]
• Disable WebRTC entirely to prevent leaking internal IP addresses (Firefox < 42)
• Don't reveal your internal IP when WebRTC is enabled (Firefox >= 42) [ 1 2 ]
• Disable WebRTC getUserMedia, screen sharing, audio capture, video capture [ 1 2 3 ]
• Disable battery API (Firefox < 52) [ 1 2 ]
• Disable telephony API [ 1 ]
• Disable "beacon" asynchronous HTTP transfers (used for analytics) [ 1 ]
• Disable clipboard event detection (onCut/onCopy/onPaste) via Javascript [ 1 2 ]
• Disable "copy to clipboard" functionality via Javascript (Firefox >= 41) [ 1 2 ]
• Disable speech recognition [ 1 2 3 ]
• Disable speech synthesis [ 1 ]
• Disable sensor API [ 1 ]
• Disable pinging URIs specified in HTML ping= attributes [ 1 ]
• When browser pings are enabled, only allow pinging the same host as the origin page [ 1 ]
• Disable gamepad API to prevent USB device enumeration [ 1 2 ]
• Disable virtual reality devices APIs [ 1 2 ]
• Disable vibrator API
• Disable Archive API (Firefox < 54) [ 1 2 ]
• Disable webGL [ 1 2 ]
• When webGL is enabled, use the minimum capability mode
• When webGL is enabled, disable webGL extensions [ 1 ]
• When webGL is enabled, force enabling it even when layer acceleration is not supported [ 1 ]
• When webGL is enabled, do not expose information about the graphics driver [ 1 2 ]
• Spoof dual-core CPU [ 1 2 ]
• Disable WebAssembly [ 1 2 3 ]

Misc

Settings that do not belong to other sections or are user specific preferences.

• Disable face detection
• Disable GeoIP lookup on your address to set default search engine region [ 1 2 ]
• Set Accept-Language HTTP header to en-US regardless of Firefox localization [ 1 ]
• Don't use OS values to determine locale, force using Firefox locale setting [ 1 ]
• Don't use Mozilla-provided location-specific search engines
• Do not automatically send selection to clipboard on some Linux platforms [ 1 ]
• Prevent leaking application locale/date format using JavaScript [ 1 2 ]
• Do not submit invalid URIs entered in the address bar to the default search engine [ 1 ]
• Don't trim HTTP off of URLs in the address bar. [ 1 ]
• Disable preloading of autocomplete URLs. [ 1 ]
• Don't try to guess domain names when entering an invalid domain name in URL bar [ 1 ]
• When browser.fixup.alternate.enabled is enabled, strip password from 'user:password@...' URLs [ 1 ]
• Send DNS request through SOCKS when SOCKS proxying is in use [ 1 ]
• Don't monitor OS online/offline connection state [ 1 ]
• Enforce Mixed Active Content Blocking [ 1 2 3 ]
• Enforce Mixed Passive Content blocking (a.k.a. Mixed Display Content)
• Disable JAR from opening Unsafe File Types [ 1 ]
• Set File URI Origin Policy [ 1 ]
• Disable Displaying Javascript in History URLs [ 1 ]
• Disable asm.js [ 1 2 3 4 ]
• Disable SVG in OpenType fonts [ 1 2 ]
• Disable video stats to reduce fingerprinting threat [ 1 2 3 ]
• Don't reveal build ID
• Don't use document specified fonts to prevent installed font enumeration (fingerprinting) [ 1 2 3 ]
• Enable only whitelisted URL protocol handlers [ 1 2 3 4 5 6 ]
• Always block media autoplay [ 1 ]

Extensions / plugins

Harden preferences related to external plugins

• Ensure you have a security delay when installing add-ons (milliseconds) [ 1 2 ]
• Require signatures [ 1 ]
• Opt-out of add-on metadata updates [ 1 ]
• Opt-out of themes (Persona) updates [ 1 ]
• Disable Flash Player NPAPI plugin [ 1 ]
• Disable Java NPAPI plugin
• Disable sending Flash Player crash reports
• When Flash crash reports are enabled, don't send the visited URL in the crash report
• When Flash is enabled, download and use Mozilla SWF URIs blocklist [ 1 2 ]
• Disable Gnome Shell Integration NPAPI plugin
• Enable plugins click-to-play [ 1 2 ]
• Updates addons automatically [ 1 ]
• Enable add-on and certificate blocklists (OneCRL) from Mozilla [ 1 2 3 4 5 ]
• Decrease system information leakage to Mozilla blocklist update servers [ 1 ]
• Disable system add-on updates (hidden & always-enabled add-ons from Mozilla) [ 1 2 3 4 ]

Firefox (anti-)features / components

Disable Firefox integrated metrics/reporting/experiments, disable potentially insecure/invasive/undesirable features

• Disable Extension recommendations (Firefox >= 65) [ 1 2 ]
• Disable WebIDE [ 1 2 ]
• Disable remote debugging [ 1 2 ]
• Disable Mozilla telemetry/experiments [ 1 2 3 4 5 6 7 8 9 10 ]
• Disable daily usage ping [ 1 ]
• Disallow Necko to do A/B testing [ 1 ]
• Disable sending Firefox crash reports to Mozilla servers [ 1 2 3 4 ]
• Disable sending reports of tab crashes to Mozilla (about:tabcrashed), don't nag user about unsent crash reports [ 1 ]
• Disable FlyWeb (discovery of LAN/proximity IoT devices that expose a Web interface) [ 1 2 3 4 ]
• Disable the UITour backend [ 1 ]
• Enable Firefox Tracking Protection [ 1 2 3 4 5 ]
• Enable contextual identity Containers feature (Firefox >= 52)
• Enable Firefox's anti-fingerprinting mode ("resist fingerprinting" or RFP) (Tor Uplift project) [ 1 2 3 ]
• disable mozAddonManager Web API [FF57+] [ 1 2 3 4 5 ]
• disable showing about:blank/maximized window as soon as possible during startup [FF60+] [ 1 ]
• Disable the built-in PDF viewer [ 1 2 3 ]
• Disable collection/sending of the health report (healthreport.sqlite*) [ 1 2 ]
• Disable Shield/Heartbeat/Normandy (Mozilla user rating telemetry) [ 1 2 3 4 5 6 7 8 ]
• Disable Firefox Hello metrics collection [ 1 ]
• Enforce checking for Firefox updates [ 1 ]
• Enable blocking reported web forgeries [ 1 2 3 4 ]
• Enable blocking reported attack sites [ 1 ]
• Disable querying Google Application Reputation database for downloaded binary files [ 1 2 ]
• Disable Pocket [ 1 2 ]
• Disable "Recommended by Pocket" in Firefox Quantum
• Enable Global Privacy Control (GPC) (Firefox >= 120) [ 1 2 3 ]
• Hide weather on New Tab

Automatic connections

Prevents the browser from auto-connecting to some Mozilla services, and from predictively opening connections to websites during browsing.

• Disable prefetching of URLs [ 1 2 ]
• Disable DNS prefetching [ 1 2 ]
• Disable the predictive service (Necko) [ 1 ]
• Reject .onion hostnames before passing the to DNS [ 1 ]
• Disable search suggestions in the search bar [ 1 ]
• Disable "Show search suggestions in location bar results"
• When using the location bar, don't suggest URLs from browsing history
• Disable Firefox Suggest [ 1 2 ]
• Disable SSDP [ 1 ]
• Disable automatic downloading of OpenH264 codec [ 1 2 ]
• Disable speculative pre-connections [ 1 2 ]
• Disable downloading homepage snippets/messages from Mozilla [ 1 2 ]
• Never check updates for search engines [ 1 ]
• Disable automatic captive portal detection (Firefox >= 52.0) [ 1 2 ]
• Disable (parts of?) "TopSites"

HTTP

HTTP protocol related entries. This affects cookies, the user agent, referer and others.

• Disallow NTLMv1 [ 1 ]
• Enable CSP 1.1 script-nonce directive support [ 1 ]
• Enable Content Security Policy (CSP) [ 1 2 ]
• Enable Subresource Integrity [ 1 2 ]
• Don't send referer headers when following links across different domains [ 1 2 3 4 ]
• Trim HTTP referer headers to only send the scheme, host, and port [ 1 ]
• When sending Referer across domains, only send scheme, host, and port in the Referer header [ 1 ]
• Accept Only 1st Party Cookies [ 1 ]
• Enable first-party isolation [ 1 2 3 ]
• Make sure that third-party cookies (if enabled) never persist beyond the session. [ 1 2 3 ]

Caching

Enable and configure private browsing mode, don't store information locally during the browsing session

• Permanently enable private browsing mode [ 1 2 ]
• Do not download URLs for the offline cache [ 1 ]
• Clear history when Firefox closes [ 1 ]
• Set time range to "Everything" as default in "Clear Recent History"
• Clear everything but "Site Preferences" in "Clear Recent History"
• Don't remember browsing history
• Don't remember recently closed tabs
• Disable disk cache [ 1 ]
• Disable Caching of SSL Pages
• Disable download history
• Disable password manager (use an external password manager!)
• Disable form autofill, don't save information entered in web page forms and the Search Bar
• Cookies expires at the end of the session (when the browser closes) [ 1 ]
• Require manual intervention to autofill known username/passwords sign-in forms [ 1 2 ]
• Disable formless login capture [ 1 ]
• When username/password autofill is enabled, still disable it on non-HTTPS sites [ 1 ]
• Show in-content login form warning UI for insecure login fields [ 1 ]
• Delete Search and Form History
• Clear SSL Form Session Data [ 1 ]
• Delete temporary files on exit [ 1 ]
• Do not create screenshots of visited pages (relates to the "new tab page" feature) [ 1 2 ]
• Don't fetch and permanently store favicons for Windows .URL shortcuts created by drag and drop
• Disable bookmarks backups (default: 15) [ 1 ]
• Disable downloading of favicons in response to favicon fingerprinting techniques [ 1 2 3 ]

UI related

Improve visibility of security-related elements, mitigate shoulder-surfing

• Enable insecure password warnings (login forms in non-HTTPS pages) [ 1 2 3 ]
• Disable "Are you sure you want to leave this page?" popups on page close [ 1 ]
• Disable Downloading on Desktop
• Always ask the user where to download [ 1 ]
• Disable the "new tab page" feature and show a blank tab instead [ 1 2 ]
• Disable Snippets [ 1 2 ]
• Disable Activity Stream [ 1 ]
• Disable new tab tile ads & preload [ 1 2 3 4 5 ]
• Disable Mozilla VPN ads on the about:protections page [ 1 2 3 4 ]
• Enable Auto Notification of Outdated Plugins (Firefox < 50) [ 1 ]
• Force Punycode for Internationalized Domain Names [ 1 2 3 4 5 ]
• Disable inline autocomplete in URL bar [ 1 ]
• Disable CSS :visited selectors [ 1 2 ]
• Disable URL bar autocomplete and history/bookmarks suggestions dropdown [ 1 ]
• Do not check if Firefox is the default browser
• When password manager is enabled, lock the password storage periodically
• Lock the password storage every 1 minutes (default: 30)
• Display a notification bar when websites offer data for offline use [ 1 ]

Cryptography

TLS protocol related settings

• Enable HTTPS-Only Mode [ 1 2 ]
• Enable HSTS preload list (pre-set HSTS sites list provided by Mozilla) [ 1 2 3 ]
• Enable Online Certificate Status Protocol [ 1 2 3 4 5 6 7 8 ]
• Enable OCSP Stapling support [ 1 2 3 ]
• Enable OCSP Must-Staple support (Firefox >= 45) [ 1 2 3 ]
• Disable TLS Session Tickets [ 1 2 3 4 5 ]
• Only allow TLS 1.[2-3] [ 1 ]
• Disable insecure TLS version fallback [ 1 2 ]
• Enforce Public Key Pinning [ 1 2 ]
• Disallow SHA-1 [ 1 2 ]
• Warn the user when server doesn't support RFC 5746 ("safe" renegotiation) [ 1 2 ]
• Disallow connection to servers not supporting safe renegotiation [ 1 2 3 ]
• Disable automatic reporting of TLS connection errors [ 1 ]
• Pre-populate the current URL but do not pre-fetch the certificate in the "Add Security Exception" dialog [ 1 2 ]
• Encrypted SNI (when TRR is enabled) [ 1 2 3 ]
• Disable the Enterprise Roots preference [ 1 2 ]

Cipher suites

This section tweaks the cipher suites used by Firefox. The idea is to support only the strongest ones with emphasis on forward secrecy, but without compromising compatibility with all those sites on the internet. As new crypto related flaws are discovered quite often, the cipher suites can be tweaked to mitigate these newly discovered threats.

• Disable null ciphers
• Disable SEED cipher [ 1 ]
• Disable 40/56/128-bit ciphers
• Disable RC4 [ 1 2 3 4 ]
• Disable 3DES (effective key size is < 128) [ 1 2 3 ]
• Disable ciphers with ECDH (non-ephemeral)
• Disable 256 bits ciphers without PFS
• Disable non-ECDHE RSA ciphers [ 1 ]
• Enable ChaCha20 and Poly1305 (Firefox >= 47) [ 1 2 3 4 5 ]
• Disable ciphers susceptible to the logjam attack [ 1 ]
• Disable ciphers with DSA (max 1024 bits)
• Disable ciphers with CBC & SHA-1
• Enable X25519Kyber768Draft00 (post-quantum key exchange) [FF Nightly 2024-01-18+] [ 1 2 3 ]

---

Further hardening

This is not enough! Here's some other tips how you can further harden Firefox:

• By default your browser trusts 100's of Certificate Authorities (CAs) from various organizations to guarantee privacy of your encrypted communications with websites. Some CAs have been known for misusing or deliberately abusing this power in the past, and a single malicious CA can compromise all your encrypted communications! To workaround this you may want to inspect the list of trusted certificates. [1]
• Keep your browser updated! If you check Firefox's security advisories, you'll see that pretty much every new version of Firefox contains some security updates. If you don't keep your browser updated, you've already lost the game.
• Disable/uninstall all unnecessary extensions and plugins!
• Use long and unique passwords/passphrases for each website/service.
• Prefer open-source, reviewed and audited software and operating systems whenever possible.
• Do not transmit information meant to be private over unencrypted communication channels.
• Use a search engine that doesn't track its users, and set it as default search engine.
• If a plugin is absolutely required, check for plugin updates
• Create different profiles for different purposes
• Change the Firefox's built-in tracking protection to use the strict list
• Change the timezone for Firefox by using the TZ environment variable (see here) to reduce it's value in browser fingerprinting
• If you are concerned about more advanced threats, use specialized hardened operating systems and browsers such as Tails or Tor Brower Bundle
• Do Not Track (DNT) is not set in the user.js and is left for the user to decide (see #11)

Add-ons

Here is a list of the most essential security and privacy enhancing add-ons that you should consider using:

• uBlock Origin
  • For additional protection, enable more blocklists in the addon dashboard.
  • For additional protection, set it to Hard mode (experienced users) - the default is Easy mode
• Cookie AutoDelete - when a tab closes, any cookies not being used are automatically deleted. Whitelist the ones you trust while deleting the rest.
• NoScript
• Decentraleyes

Additional add-ons that you might consider using or reading about:

• uMatrix (experienced users)
• Privacy Badger
• Mozilla Lightbeam
• PRISM Break Web Browser Addons section
• Ghostery (proprietary software, maintained by an advertising company)

Known problems and limitations

Hardening your often implies a trade-off with ease-of-use and comes with reduced functionality. Here is a list of known problems/limitations:

• Disabling ServiceWorkers breaks functionality on some sites (Google Street View...)
• Disabling ServiceWorkers breaks Firefox Sync
• Disabling DOM timing API breaks item pages in AliExpress (https://github.com/pyllyukko/user.js/issues/561)
• Disabling resource timing API breaks some DDoS protection pages (Cloudflare)
• Web Audio API is required for Unity web player/games
• Disabling WebRTC breaks peer-to-peer file sharing tools (reep.io ...)
• Disabling clipboard events breaks Ctrl+C/X/V copy/cut/paste functionaility in JS-based web applications (Google Docs...)
• Disabling clipboard operations will break legitimate JS-based "copy to clipboard" functionality
• Disabling WebGL breaks WebGL-based websites/applications (windy, meteoblue...)
• WebAssembly is required for Unity web player/games
• Enabling Mixed Display Content blocking can prevent images/styles... from loading properly when connection to the website is only partially secured
• Disabling nonessential protocols breaks all interaction with custom protocols such as mailto:, irc:, magnet: ... and breaks opening third-party mail/messaging/torrent/... clients when clicking on links with these protocols
• Disabling system add-on updates prevents Mozilla from "hotfixing" your browser to patch critical problems (one possible use case from the documentation)
• Containers are not available in Private Browsing mode
• RFP breaks some keyboard shortcuts used in certain websites (see #443)
• RFP changes your time zone
• RFP breaks some DDoS protection pages (Cloudflare)
• Fully automatic updates are disabled and left to package management systems on Linux. Windows users may want to change this setting.
• Update check page might incorrectly report Firefox ESR as out-of-date
• Do No Track must be enabled manually
• Blocking referers across same eTLD sites breaks some login flows relying on them, consider lowering this pref to 1
• Blocking 3rd-party cookies breaks a number of payment gateways
• First-party isolation breaks Microsoft Teams
• First-party isolation causes HTTP basic auth to ask for credentials for every new tab (see #425)
• You can not view or inspect cookies when in private browsing: https://bugzilla.mozilla.org/show_bug.cgi?id=823941
• When Javascript is enabled, Websites can detect use of Private Browsing mode
• Private browsing breaks Kerberos authentication
• Disables "Containers" functionality (see below)
• "Always use private browsing mode" (browser.privatebrowsing.autostart) disables the possibility to use password manager: https://support.mozilla.org/en-US/kb/usernames-and-passwords-are-not-saved#w_private-browsing
• Installing user.js will remove your browsing history, caches and local storage.
• Installing user.js will remove your saved passwords (https://github.com/pyllyukko/user.js/issues/27)
• Clearing open windows on Firefox exit causes 2 windows to open when Firefox starts https://bugzilla.mozilla.org/show_bug.cgi?id=1334945
• .URL shortcut files will be created with a generic icon
• disabling "beforeunload" events may lead to losing data entered in web forms
• OCSP leaks your IP and domains you visit to the CA when OCSP Stapling is not available on visited host
• OCSP is vulnerable to replay attacks when nonce is not configured on the OCSP responder
• OCSP adds latency (performance)
• Short-lived certificates are not checked for revocation (security.pki.cert_short_lifetime_in_days, default:10)
• Firefox falls back on plain OCSP when must-staple is not configured on the host certificate
• security.OCSP.require will make the connection fail when the OCSP responder is unavailable
• security.OCSP.require is known to break browsing on some captive portals

In addition see the current issues. You can use the web console to investigate what causes websites to break.

---

FAQ

Does this user.js file fix all security problems?

No. Please read Known problems and limitations, the project's issue tracker, and report new issues there. Please open separate issues for each individual problem/question you may have.

Why are obsolete/deprecated entries included in the user.js file?

This project is aimed at Firefox versions between the current ESR and the latest Firefox release. We will wait for widespread deployment of the current ESR (eg. adoption in major Linux distributions) before removing deprecated/obsolete preferences. Presence of deprecated entries causes no known problems.

Installing the user.js file breaks xyz plugin/addon/extension, how can I fix it?

See https://github.com/pyllyukko/user.js/issues/100

Will there be an official addon/an android version/feature xyz?

Search the project issues.

How can I lock my preferences to prevent Firefox overwriting them?

See lockPref in System-wide installation.

Contributing

Yes please! All issues and pull requests are more than welcome. Please try to break down your pull requests or commits into small / manageable entities, so they are easier to process. All the settings in the user.js file should have some official references to them, so the effect of those settings can be easily verified from Mozilla's documentation.

Feel free to follow the latest commits RSS feed and other interesting feeds from the References section.

You may also reach other contributors through IRC (#user.js on Freenode) or Gitter.

For more information, see CONTRIBUTING

---

Online tests

Version checks

• Mozilla Plugin Check
• Adobe Flash Player Version Check
• Java Version Check

Fingerprinting tests

• BrowserSpy.dk
• BrowserLeaks.com
• AmIUnique [1]
• Panopticlick
• Unique Machine
• Firefox Addon Detector [1]
• AudioContext Fingerprint Test Page
• Evercookie
• WebRTC Test Landing Page
• getUserMedia Test Page
• Onion test for CORS and WebSocket
• Official WebGL check
• WebGL Report
• Battery API [1]
• WebRTC LAN address leak test
• IP Check
• OONI Internet censorship tests

SSL tests

• SSL Client Test
• How's My SSL
• Mixed content tests (Mozilla)
• Mixed content tests (Microsoft)
• SSL Checker | Symantec CryptoReport
• Bad SSL

Other tests

• Test page for Firefox's built-in Tracking Protection
• Test page for Firefox's built-in Phishing Protection ("Web forgeries")
• Test page for Firefox's built-in Malware Protection (attack page)
• Test page for Firefox's built-in Malware Protection (unwanted software)
• HTML5test - Comparison of supported HTML5 features in various browsers/versions
• Filldisk
• BrowserAudit

---

References

Mozilla documentation

• Security Advisories for Firefox
• Known Vulnerabilities for Firefox
• DXR - Firefox General preferences (RSS)
• DXR - Firefox Security preferences (RSS)
• DXR - Firefox Datareporting preferences (RSS)
• DXR - Firefox Healthreport preferences (RSS)
• Mozilla Security Blog (RSS)
• Mozilla Firefox Release Plan
• Mozilla Firefox developer release notes
• Advices from Mozilla Firefox on privacy and government surveillance
• Polaris - advance privacy technology for the web
• Mozilla Privacy Principles
• List of Firefox "about:" URLs
• A brief guide to Mozilla preferences
• Mozilla preferences for uber-geeks
• Privacy & Security related add-ons (RSS)
• libpref — Firefox Source Docs documentation
• Firefox Source Tree documentation

Other documentation

• User.js comparator
• CVEs for Firefox - mitre.org
• CVEs for Firefox - cvedetails.com
• About:config entries - MozillaZine
• Security and privacy-related preferences - MozillaZine
• Diff between various Firefox .js configurations in upcoming releases (RSS)
• Center for Internet Security - Mozilla Firefox benchmarks (RSS)
• iSEC Tor Browser evaluation
• The Design and Implementation of the Tor Browser
• Browser Exploitation Framework [1 2 3]
• shadow - Firefox jemalloc heap exploitation framework

TLS/SSL documentation

• Mozilla Included CA Certificate List
• Potentially problematic CA practices
• Bulletproof SSL and TLS
• TLS Cipher Suite Discovery
• Server-side TLS configuration

---

Maintenance

Run make help to get a list of makefile targets used for frequent maintenance operations.

$ make help 
locked_user.js      generate a locked configuration file
systemwide_user.js  generate a system-wide configuration file
debian_locked.js    generate a locked, system-wide configuration file
policies.json       generate policy file (https://github.com/mozilla/policy-templates/blob/master/README.md)
tests               run all tests
test-acorn          validate user.js syntax
test-shellcheck     check/lint shell scripts
000-tor-browser.js  download Tor Browser custom configuration reference
diff-tbb            differences between values from this user.js and tor browser's values
diff-tbb-2          differences between values from this user.js and tor browser's values (alternate method)
diff-tbb-missing-from-user.js           preferences that are present in tor browser's defaults, but not in this user.js
diff-sourceprefs.js download and sort all known preferences files from Firefox (mozilla-central) source
diff-upstream-duplicates                preferences with common values with default Firefox configuration
diff-upstream-missing-from-user.js      preferences present in firefox source but not covered by user.js
diff-upstream-deprecated                preferences in hardened user.js that are no longer present in firefox source
diff-stats          count preferences number, various stats
clean               clean automatically generated files/build/test artifacts
doc-whatdoesitdo    generate the README "What does it do?" section
doc-toc             generate the README table of contents
help                generate list of targets with descriptions

---