It's a shame that the actual attack mechanism doesn't seem to be detailed on the github repo, and the link to the article is dead.
Supercookie: Browser Fingerprinting via Favicon (2021)
21–30 of 105 posts
Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#22Probably not a popular opinion here but i'm honestly impressed that someone made this work?
There is ad money at stake, and it is unfortunately one of the key revenue models in the modern web. I don't know if this particular research was sponsored by ad-tech or if it's preventive, but it shouldn't be generally surprising that this kind of things are heavily researched.
Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#23I don't understand the live demo
it gave me some ID, but how do I test that some different website can track me resulting in same ID?
or is it only "detect private browsing/container on same browser" kind of stuff?
Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#24I just got a refresh per second and a counter from 1/18 to 18/18 and repeat. Feels like I wasted 20s.
Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#25Needs a (2023) addition in the title
make it 2021 actually. After these years, was this fixed?
Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#26I got different IDs in regular browsing vs incognito mode in Firefox.
I got different IDs in regular browsing vs my first incognito window vs my second incognito window.
Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#27Nonpersistent vm-based browser, I use qemu + cage + firefox and some glue logic to fire up a copy of a base image which gets deleted on exit. Fires up slower than a native firefox instance but runs all the same.
Can containerize for the less paranoid and less work but browsers touching host kernel gives me the ick as does the idea of trying to write ebpf policies for firefox to mitigate. Browsers are pain.
Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#28I have never liked how Safari always tries to reload favicons. Seems like an obvious and annoying privacy leak.
Re: Supercookie: Browser Fingerprinting via Favicon (2021)
#29Nonpersistent vm-based browser, I use qemu + cage + firefox and some glue logic to fire up a copy of a base image which gets deleted on exit. Fires up slower than a native firefox instance but runs all the same. Can containerize for the less paranoid and less work but browsers touching host kernel gives me the ick as does the idea of trying to write ebpf policies for firefox to mitigate. Browsers are pain.
This sounds interesting, do you have this written up anywhere?