about:config fingerprinting class unexpected behavior
Categories
(Core :: Privacy: Anti-Tracking, defect)
Tracking
()
People
(Reporter: lee.smith.93, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0
Steps to reproduce:
Setting the following to TRUE or 1
privacy.resistFingerprinting.randomization.enabled
privacy.resistFingerprinting.randomDataOnCanvasExtract
Whilst parent class set to FALSE or 0
privacy.resistFingerprinting
Actual results:
Our config is completely ignored when the parent class is set to FALSE yet the children are set to TRUE
privacy.resistFingerprinting.randomization.enabled
privacy.resistFingerprinting.randomDataOnCanvasExtract
Expected results:
I expect the CanvasExtract to be randomized, but it isnt.
However, setting privacy.resistFingerprinting to TRUE or 1, and the other two to FALSE or 0, the canvas would be randomized, despite instructing the child classes not to randomize.
Inconsistent and unexpected behavior
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Privacy: Anti-Tracking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•2 years ago
|
||
Thanks for reporting,
The pref privacy.resistFingerprinting controls the fingerprinting resistance mode. So, no fingerprinting resistance feature would apply if you disable the pref.
In the second case, the pref privacy.resistFingerprinting.randomization.enabled is no longer supported. So, we cannot disable canvas randomization alone while fingerprinting resistance is enabled. The pref privacy.resistFingerprinting.randomDataOnCanvasExtract controls a different randomization mechanism. Disabling it should work, but the canvas randomization will still apply so that the canvas data is still randomized.
I will close this bug for now given that the behavior is expected.
Description
•