Fingerprinting by detecting CanvasBlocker
See original GitHub issuePoC: https://jsfiddle.net/6ke4ycmb/
In case you don’t want to click a link and execute my JS here’s the code:
var canvas = document.createElement('canvas');
var ctx = canvas.getContext("2d");
var canvasBlocker=false;
try{
ctx.getImageData(0,0,0,0);
}catch(err){
try{
console.log(err.name);
}catch(err2){
canvasBlocker=true;
}
}
if(canvasBlocker){
alert("Canvas blocker detected.");
}else{
alert("No canvas blocker detected");
}
This reliably recognized if CanvasBlocker is in use in my tests. Thus providing another bit for fingerprinting 😦
Not sure how exactly this can be fixed though, as I’m not familiar with Firefox Extensions.
Issue Analytics
- State:
- Created 6 years ago
- Comments:18 (12 by maintainers)
Top Results From Across the Web
Canvas Blocker - Fingerprint Protect
This extension protects user privacy by prevents the HTML canvas element from being used by malicious scripts for fingerprinting the user.
Read more >CanvasBlocker – Get this Extension for Firefox (en-US)
This add-on allows users to prevent websites from using some Javascript APIs to fingerprint them. Users can choose to block the APIs ...
Read more >Canvas Fingerprinting Guide: The Good, the Bad and The Ugly
There's no doubt that we are being tracked online for both good and bad reasons. According to a study by Ghostery, a renowned...
Read more >How canvas fingerprint blockers make you easily trackable
Learn how canvas fingerprint blocking does not in fact stop account bans - but instead causes them.
Read more >HTML5 Canvas Fingerprinting - BrowserLeaks
Browser Fingerprinting with no user agent identifiers, only through the HTML5 ... Browser Detection via Canvas is very rude and nominal, based just...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Finally got rid of the technical problems there. The picture will remain like that in the future.
Some upvotes can’t hurt. But I think all their ressources are blocked by the move to webExtensions. There are still APIs missing.