Split up RealmBehaviors::shouldResistFingerprinting
Categories
(Core :: Security, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox116 | --- | fixed |
People
(Reporter: tschuster, Assigned: tschuster)
References
Details
Attachments
(3 files)
Currently the JS engine just gets one config option for enabling/disabling RFP mode. Instead we should have a realm option for every configurable feature.
Comment 1•3 years ago
|
||
Instead of different realm options, could we possibly give it a uint32/uint64/BitSet with the enabled RFPTargets? Maybe we could add a reserved bit that indicates 'AllTargets', to be used for RFP mode, and then that bit is cleared for FPP and it checks individual targets?
| Assignee | ||
Comment 2•3 years ago
|
||
I don't think that extensibility is really necessary. (We would also need to move RFPTarget to some place that is accessible to the JS engine) I think right now we would only need two options: forceUTCTimezone and forceFdlibm. I doubt that there are going to be many more sources of fingerprinting added to JS. And we do have some other ways of fingerprinting protection we already use anyway that don't need a flag, at least JS::SetReduceMicrosecondTimePrecisionCallback.
Comment 3•3 years ago
|
||
Hm, okay I figured there'd be a half dozen things we'd need, if it's only 2 or 3....
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 4•3 years ago
|
||
| Assignee | ||
Comment 5•3 years ago
|
||
Depends on D179534
| Assignee | ||
Comment 6•3 years ago
|
||
Tom, please have a look at the question about WokerPrivate::ShouldResistFingerprinting.
Updated•3 years ago
|
| Assignee | ||
Comment 7•3 years ago
|
||
Updated•3 years ago
|
Updated•3 years ago
|
Comment 9•3 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/5a69fb7b90ba
https://hg.mozilla.org/mozilla-central/rev/740c98ec8491
https://hg.mozilla.org/mozilla-central/rev/655c1ec8a538
Description
•