97
Share your coveryourtracks score!
(coveryourtracks.eff.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 01 Nov 2023
97 points (97.1% liked)
Privacy
32177 readers
676 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
Completely vanilla, fully stopped and restarted the browser. This was right after the 13.0 update.
For what it's worth I just tested.
Tor browser 13.0.1, plus U-Block origin, fingerprint.com did not identify two different sessions
I should test again then, not sure what happened
Just did a fresh install on Linux (fresh download too) and unfortunately, with no settings changed except security to "Safer", it once again identified me across multiple sessions.
FWIW it does change my ID if I resize the window enough to jump to a different size letterbox.
Edit: forgot to mention, the fresh install got a different ID ti the previous install.
Something is very curious about your install.
if you want to debug this: in tor browser, double check your using tor, try out whatismyipaddress.com, change circuits and make sure it changes again.
Look at the bits of entropy that coveryourtracks.eff.org shows, it could be something funky like an environment variable letting in system fonts.
Yeah I'll do some investigating, good to know that the Tor browser isn't at fault though (I probably should've operated under this assumption in the first place).