-
-
Notifications
You must be signed in to change notification settings - Fork 388
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
Block canvas & cache based evercookie #616
Comments
@ghostwords any ideas? |
It seems that the canvas fingerprinting function (if that is what it is ...) writes to the canvas element using drawImage, which is not one of the "write methods" we currently support. If so, this wouldn't get picked up for canvas fingerprinting on any browser. |
After adding
and
I had to temporarily disable both text length (needs to be updated for |
I guess we should add |
Yes, just not sure when. To clarify, when I said I added |
I think this is canvas & cache based evercookie, not canvas fingerprinting. Check Samy's evercookie code or read How does the PNG caching work? The only difference is that t4ft.de script uses GIF, instead of PNG. The script draws an image loaded from http://c.t4ft.de/ckgif/ (or cache) into the canvas. The image, which is immediately cached, contains the RGB encoded user ID. Even if you remove your cookies or local storage, the script can draw the cached image into the canvas and read your ID using canvas This behavior is conditionally triggered and doesn't run for me at the moment, but I can see different GIF contents when I load the ckgif URL with different profiles. You can see the request to http://c.t4ft.de/ckgif/ on HTTP Archive. The script also uses ETag based evercookie. Base64 decoding the ftgnetid cookie content gives you the ETag value (thanks to light obfuscation.) For instance in the above HTTP Archive example, ETag=71151108140103233, ftgnetid=NzExNTExMDgxNDAxMDMyMzM=. |
Dang! Good work @gunesacar, we really need to start adding heuristics to detect other types of supercookies I guess. |
detection: etag supercookies |
I've noticed that the firefox version (fresh install + clean install of browser and extensions) detects the c.t4ft.de domain referenced in golem.de and zeit.de as fingerprinting website.
Going to the page in a fresh chrome installation (browser and extension) shows this domain under non-tracking domains. But looking at the script http://c.t4ft.de/c/ftg_iq.min.js shows that it does canvas fingerprinting. This is also the reason why this domain gets blocked after a while in firefox but not in chrome
As said earlier, both were fresh installations with fresh user profiles. Both browsers only had privacy badger and https everywhere installed,
The text was updated successfully, but these errors were encountered: