Closed Bug 1425130 Opened 7 years ago Closed 2 years ago

Sensor API exposes a High-Res timestamp

Categories

(Core :: DOM: Security, enhancement, P3)

Product:
Core
Component:
DOM: Security
Type:
enhancement

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1432631
Tracking Flags:
Tracking Status
firefox59 --- affected

People

(Reporter: tjr, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [fingerprinting][domsecurity-backlog1][fp-triaged])

https://w3c.github.io/sensors/#model-sensor We'll need to make sure this is rounded. We'll also need to make sure that the frequency of readings from any/all sensors are limited to no more often than the rounding value.
Priority: -- → P3
Whiteboard: [fingerprinting] → [fingerprinting][domsecurity-backlog1]
P2 to investigate
Priority: P3 → P2
Since Sensor API hasn't implemented in Firefox yet, so I think we can put this as P3. However, we should still keep eye on this; making sure the timestamp is always rounded in fingerprinting resistance mode as long as this API is implemented.
Priority: P2 → P3
Blocks: uplift_tor_fingerprinting
Whiteboard: [fingerprinting][domsecurity-backlog1] → [fingerprinting][domsecurity-backlog1][fp-triaged]
IMHO it's better not to implement the API at all.
Severity: normal → S3

I expect that any sensor implementation if it happens will expose timestamps in the standard way we expose all timestamps in Firefox, and therefore be protected as expected. We don't need this bug hanging around.

Status: NEW → RESOLVED
Closed: 2 years ago
Duplicate of bug: 1432631
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.