Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

Tell me about config setting "privacy.resistFingerprinting" TRUE vs CanvasBlocker etc AddOns

more options

If I set privacy.resistFingerprinting to true, should I disable things like CanvasBlocker, which says: > This add-on allows users to prevent websites from using some Javascript APIs to fingerprint them.

Users can choose to block the APIs entirely on some or all websites (which may break some websites) or fake its fingerprinting-friendly readout API. ... IMPORTANT: you should only have ONE addon/setting set that protects an API. Otherwise you could face massive performance issues. ...

But setting privacy.resistFingerprinting to true and/or using the new fingerprinting protection introduced with Firefox 67 is fine.

Protected "fingerprinting" APIs: canvas 2d webGL audio history window (disabled by default) DOMRect navigator (disabled by default) screen

If I set privacy.resistFingerprinting to true, should I disable things like CanvasBlocker, which says: > This add-on allows users to prevent websites from using some Javascript APIs to fingerprint them. Users can choose to block the APIs entirely on some or all websites (which may break some websites) or fake its fingerprinting-friendly readout API. ... IMPORTANT: you should only have ONE addon/setting set that protects an API. Otherwise you could face massive performance issues. ... But setting privacy.resistFingerprinting to true and/or using the new fingerprinting protection introduced with Firefox 67 is fine. Protected "fingerprinting" APIs: canvas 2d webGL audio history window (disabled by default) DOMRect navigator (disabled by default) screen

All Replies (3)

more options

The Fingerprinting block under Tracking Protection uses a short list of servers known to compute or track fingerprints. Simple. Turn or keep that on.

I personally do not think the results of using the privacy.resistFingerprinting preference are worth the trouble. Telling the world a different Firefox version, different screen resolution, and potentially a different OS, and overriding site zoom levels, may make it harder for fingerprinters to ascertain the true values, but they may not make your browser look less unique.

I don't know about the other comments. What is the source?

more options

quote is from Canvasblocker addon info page

FF ver 68.3.0 esr does not seem to have "Fingerprinting block under Tracking Protection "

more options

FireFoxSucks said

FF ver 68.3.0 esr does not seem to have "Fingerprinting block under Tracking Protection "

ESR will pick up the newer features from Firefox 69-77 when it moves to Firefox 78 as its base. Or whatever later version it turns out to be.