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

Nightly doesn't randomize fingerprint #8911

Closed
ghost opened this issue Mar 29, 2020 · 3 comments
Closed

Nightly doesn't randomize fingerprint #8911

ghost opened this issue Mar 29, 2020 · 3 comments
Labels
closed/invalid feature/shields/fingerprint The fingerprinting (aka: "device recognition") protection provided in Shields

Comments

@ghost
Copy link

ghost commented Mar 29, 2020

Description

Fingerprint ID does not change after each reset (tried incognito and manual clearing) when tested in fingerprintjs.com/demo. Testing the fingerprint on panopticlick shows that Hash of canvas fingerprint and AudioContext fingerprint results are “randomized by first party domain”, while for Hash of WebGL fingerprint I get a constant/unchanging hash number (Might be related).

Steps to Reproduce

  1. Install fresh brave nightly.
  2. Change shield fingerprint protection to block all.
  3. Open private tab
  4. Go to fingerprintjs.com/demo
  5. Close and repeat (minus step 1).

Actual result:

Expected result:

Fingerprint ID to be different on every test in fingerprintjs.com/demo.

Reproduces how often:

Every time.

Brave version (brave://version info)

Brave 1.8.52 Chromium: 81.0.4044.83 (Official Build) unknown (64-bit)
Revision 5718ca617723806b9aacfb41108a0d911d1bde74-refs/branch-heads/4044@{#853}
OS Linux

Version/Channel Information:

No.

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields?
    No.
  • Does the issue resolve itself when disabling Brave Rewards?
    No.
  • Is the issue reproducible on the latest version of Chrome?
    No.

Miscellaneous Information:

Randomization used to work but it stopped after a few updates. This issue is also reproducible in Windows 10.

@bsclifton bsclifton added the feature/shields/fingerprint The fingerprinting (aka: "device recognition") protection provided in Shields label Mar 30, 2020
@bsclifton
Copy link
Member

cc: @pes10k

@pes10k
Copy link
Contributor

pes10k commented Mar 30, 2020

Thanks, looking into this now

@pes10k
Copy link
Contributor

pes10k commented Mar 30, 2020

@774z thank you for reporting this! From poking at this a lot, it turns out that they now ignore canvas and audio fingerprints, and try to fingerprint based on other characteristics. The most important is IP. So, Brave will give you better protections against this kind fingerprinting than other browsers, where the canvas and audio fields are used for the fingerprint. And there are more protection-through-randomization endpoints rolling out in Brave too, so things are getting better.

Also, we just started blocking this company in EasyPrivacy too, so, double protection :)

@pes10k pes10k closed this as completed Mar 30, 2020
@bbondy bbondy added this to the Closed / Invalid milestone Jun 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed/invalid feature/shields/fingerprint The fingerprinting (aka: "device recognition") protection provided in Shields
Projects
None yet
Development

No branches or pull requests

3 participants