GitHub - jonasstrehle/supercookie: ⚠️ Browser fingerprinting via favicon!
github.com⚠️ Browser fingerprinting via favicon! Contribute to jonasstrehle/supercookie development by creating an account on GitHub.
You must log in or register to comment.
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 :)
- 0 users online
- 108 users / day
- 435 users / week
- 1.32K users / month
- 4.54K users / 6 months
- 1 subscriber
- 4.45K Posts
- 112K Comments
- Modlog
Note that this is an issue from 2021. Firefox has implemented countermeasures since version 85, Chrome seems to have done the same.
So while this is definitely interesting, it shouldn‘t be an issue anymore.
Yep. I just confirmed it… restarting Firefox seems to make the ID in https://demo.supercookie.me/ change. Thought as long as you keep Firefox session open the id will be the same.
I’m not sure if the links you reference are the whole story though, because they are talking about partitioning the cache per top-level domain, which I would expect wouldn’t have been enough, since the demo is specific to its top-level domain and it’s not necessarily about cross-domain id.
makes mental note to shutdown firefox on mobile more often.
deleted by creator