Open
Bug 1522517
Opened 6 years ago
Updated 7 months ago
[meta] Unify software rendering settings while privacy.resistFingerprinting=True
Categories
(Core :: Graphics, enhancement, P2)
Core
Graphics
Tracking
()
NEW
People
(Reporter: xeonchen, Unassigned)
References
(Depends on 4 open bugs, Blocks 1 open bug)
Details
(Keywords: meta, Whiteboard: [fingerprinting][fp-triaged])
Even though software rendering may reduce the entropy being fingerprinted by websites, different versions of OSes is still fingerprintable because Windows, GNU/Linux, and macOS have variety of user settings that could change the rendering result.
So I open this meta bug here to trace potential following tasks.
Here are notes taken by :englehardt in Mozlando 2018:
- User may set different anti-aliasing settings
- Windows has a very clear dialog for toggling clear type settings.
- Monitor gamma settings
- May be pulling this indirectly. I.e., “what default rendering settings should we use” from the OS. And thus maybe the OS gives the user settings as default. Firefox has no way to know.
- Could get rid of this by hard coding the defaults. Chrome has hard coded defaults for many of these settings already, so it should be a safe things to do.
Would need to disable a variety of settings, but only in resist fingerprinting mode. Font settings can be tweaked.
- Harder to do at runtime than compile time.
- Changes would apply to all font rendering, not just canvas rendering. Might be possible to prevent with some additional work.
Reporter | ||
Updated•6 years ago
|
Priority: -- → P2
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•