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

Fail to Protect Privacy from Fingerprintjs #15825

Closed
BRAVERaaa opened this issue May 13, 2021 · 5 comments
Closed

Fail to Protect Privacy from Fingerprintjs #15825

BRAVERaaa opened this issue May 13, 2021 · 5 comments
Labels
closed/duplicate Issue has already been reported OS/Android Fixes related to Android browser functionality OS/Desktop

Comments

@BRAVERaaa
Copy link

Description

Fail to Protect Privacy from Fingerprintjs

Steps to Reproduce

  1. Open https://fingerprintjs.com/
  2. Clear all cookies and cache
  3. Close all tabs and close browser
  4. Restart and open https://fingerprintjs.com/

Actual result:

image
(I may be tracked)

Expected result:

Every time I clean cookies and cache then restart browser, the ID shown should be different.

Reproduces how often:

Every time.

Desktop Brave version:

Brave 1.24.84 Chromium: 90.0.4430.93 (x64)

Android Device details:

  • Install type (ARM, x86):ARM
  • Device type (Phone, Tablet, Phablet):Phone
  • Android version:Android 11 Brave 1.24.84 Chromium 90.0.4430.93 (x64)

Version/Channel Information:

Release

  • Can you reproduce this issue with the current release?
  • Yes
  • Can you reproduce this issue with the beta channel?
  • Yes
  • Can you reproduce this issue with the nightly channel?
  • Yes

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?
  • Yes (This should be protected by Brave)

Miscellaneous Information:

@BRAVERaaa BRAVERaaa added OS/Android Fixes related to Android browser functionality OS/Desktop labels May 13, 2021
@srirambv
Copy link
Contributor

cc: @pes10k

@pes10k
Copy link
Contributor

pes10k commented May 13, 2021

Thank you for raising this issue @BRAVERaaa! I'm going to close the issue though, for the same reasons this previous issue was closed #14031

The short of it is that the page you're referencing plays a whole bunch of games that aren't related to fingerprinting, so that their commercial product looks more impressive. For Brave users their tracking is basically just IP at this point. I expect if you visit in the same browser, but from different profiles and IPs (say in Tor mode and standard mode) you'll see they're not actually able to fingerprint you (and that they're not actually using fingerprinting values in the first place, but other unrelated identifiers like IP)

Hope that helps, and feel free to reopen the issue if you see anything different than the above!

@pes10k pes10k closed this as completed May 13, 2021
@pes10k pes10k added the closed/duplicate Issue has already been reported label May 13, 2021
@BRAVERaaa
Copy link
Author

@pes10k
Sorry for disturbing, but something different happens.
Few weeks ago, every time I clean cookies and cache then restart browser, the ID shown was different, and the IDs between normal window and incognito window were different as well.
But now, I try it again, the IDs between normal window and incognito window are the same!!! It is amazing!!!
I even have tried to change my ip, but the ID is always the same.
PNG1
PNG2

Fingerprintjs seems to have updated. Maybe this is the cause.
PNG3

@pes10k
Copy link
Contributor

pes10k commented May 17, 2021

Hi @BRAVERaaa , thanks for the heads up! I expect it might be related to this #15875, in which case, we're on the case and hope to be able to share an expected solution in the next day or three.

cc: @ShivanKaul

@Andromeda606
Copy link

same.
Despite the hash changes on this site, there is no change in software that provides really high protection like gologin. The site records everything down to audio data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed/duplicate Issue has already been reported OS/Android Fixes related to Android browser functionality OS/Desktop
Projects
None yet
Development

No branches or pull requests

4 participants