Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output of decoding and encoding bytes are fingerprintable #231

Open
jonathanKingston opened this issue May 6, 2021 · 3 comments
Open

Output of decoding and encoding bytes are fingerprintable #231

jonathanKingston opened this issue May 6, 2021 · 3 comments
Labels
editorial changes to wording, grammar, etc that don't modify the intended behavior obsolete Looks like it might be obsolete privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on.

Comments

@jonathanKingston
Copy link

Whilst playing around with the demo code on web.dev we noticed that the output of encoding is different based on the users machine.

I've not extensively tested this by any means however on different Mac machines with different hardware and the same version of Chrome the result was different.

Demo link: https://sand-freckle-pilot.glitch.me/

Example results from Mac machines:

  • New canvas id checksum 7504035
  • New frame id checksum 7502709

and:

  • New canvas id checksum 7504035
  • New frame id checksum 2040000

The differences observed should be outlined in privacy considerations.

@samuelweiler samuelweiler added the privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. label May 7, 2021
@dalecurtis
Copy link
Contributor

dalecurtis commented May 8, 2021

Have you run this test with WebRTC loopback? I would expect it shows the same issue.

@padenot
Copy link
Collaborator

padenot commented May 10, 2021

Or even MediaRecorder from a source, and then HTMLVideoElement + <canvas> + drawImage really, might be simpler to construct a test-case this way for folks less familiar with WebRTC.

(I assume it's the same encoders/decoders underneath all of those APIs, this is the case in Gecko).

@chcunningham chcunningham added the editorial changes to wording, grammar, etc that don't modify the intended behavior label May 12, 2021
@chcunningham
Copy link
Collaborator

Triage note: marking 'editorial' for additions to privacy considerations.

@Djuffin Djuffin added the obsolete Looks like it might be obsolete label Sep 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editorial changes to wording, grammar, etc that don't modify the intended behavior obsolete Looks like it might be obsolete privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on.
Projects
None yet
Development

No branches or pull requests

6 participants