Reviews for CanvasBlocker
CanvasBlocker by kkapsner
Response by kkapsner
Developer response
posted 4 years agoThe hashes change for me if I hit "Re-test your browser". Depending on the CB settings the hashes may stay the same (Random number generator). Please open an issue at https://github.com/kkapsner/CanvasBlocker/issues with your settings. Then we investigate the problem further.
Edit in response to your edit: if the hash does not change for you with CanvasBlocker it might be a bug and I want to investigate it further. But this review page is a very bad communication channel for such things (e.g. I did not get any notification that you edited your review and you have no way to actually respond). That's why you should create an issue at Github. It's not about "shuffling people off". It's about better communication and actually solving the problem and/or getting better insight.
The EFF investigation is 10 years old (CB is "only" 5 years old) and I think some improvements were made in the meantime. I can only repeat myself: on https://panopticlick.eff.org/ I get different hashes when I click "Re-test your browser".
I have two ideas why you get the same hash:
1. you have privacy.resistFingerprinting enabled which also protects canvas (see https://github.com/kkapsner/CanvasBlocker/issues/158 and https://github.com/ghacksuserjs/ghacks-user.js/issues/767 for further information)
2. you have the persistent random number generator enabled (stealth preset)
In response to your edit2: it's OK if you do not want to report a Github. At the moment I have no issue open at Github were the protection is not working - I try to solve them as quick as possible. Sometimes it's a CB bug and sometimes it's a misconfiguration or misunderstanding. If you know of other persons with failed protection maybe they want to help me to solve this issue. Without the complete details of the system and some sort of reproduction scenario I have no way of knowing what is going wrong.
I do not know which bad experiences you had with Github but it's simply a development platform and the kind of responses/interaction can vary very much between repositories. It all depends on people.
I had several issue with exactly the same symptom (hash not changing - like https://github.com/kkapsner/CanvasBlocker/issues/199 with Panopticlick or the most recent one being https://github.com/kkapsner/CanvasBlocker/issues/425). All of them were resolved or I had do close them because I did not get an answer for my following up questions that I have to prompt to solve the issue.
I do not say that Panopticlick does not maintain accurate results. I simply say that some people try to solve the problem in the last 10 years and made progress (the most know is the TOR Browser and the Firefox uplift privacy.resistFingerprinting). I know that CanvasBlocker is not perfect and there will be other fingerprinting techniques and attack vectors in the future that CB does not cover at the moment. But at the moment (and especially with the Canvas hashes on Panopticlick) it's working fine.
The "random number generator" is a setting withing the CanvasBlocker settings - I could show you a screenshot of where to find it if we were on Github...
It is set to "persistent" if you selected the "stealth" preset upon installation.
I do not see a point why Mozilla would want to buy my add-on. If they would want to incorporate it into their browser they simply could to it as it's open source and the licence allows the usage for non commercial usage (and they do charge money for Firefox). There are loads of good add-ons that work and that are not integrated into Firefox. That's the idea and beauty of Firefox: you can customize it.
Edit in response to your edit: if the hash does not change for you with CanvasBlocker it might be a bug and I want to investigate it further. But this review page is a very bad communication channel for such things (e.g. I did not get any notification that you edited your review and you have no way to actually respond). That's why you should create an issue at Github. It's not about "shuffling people off". It's about better communication and actually solving the problem and/or getting better insight.
The EFF investigation is 10 years old (CB is "only" 5 years old) and I think some improvements were made in the meantime. I can only repeat myself: on https://panopticlick.eff.org/ I get different hashes when I click "Re-test your browser".
I have two ideas why you get the same hash:
1. you have privacy.resistFingerprinting enabled which also protects canvas (see https://github.com/kkapsner/CanvasBlocker/issues/158 and https://github.com/ghacksuserjs/ghacks-user.js/issues/767 for further information)
2. you have the persistent random number generator enabled (stealth preset)
In response to your edit2: it's OK if you do not want to report a Github. At the moment I have no issue open at Github were the protection is not working - I try to solve them as quick as possible. Sometimes it's a CB bug and sometimes it's a misconfiguration or misunderstanding. If you know of other persons with failed protection maybe they want to help me to solve this issue. Without the complete details of the system and some sort of reproduction scenario I have no way of knowing what is going wrong.
I do not know which bad experiences you had with Github but it's simply a development platform and the kind of responses/interaction can vary very much between repositories. It all depends on people.
I had several issue with exactly the same symptom (hash not changing - like https://github.com/kkapsner/CanvasBlocker/issues/199 with Panopticlick or the most recent one being https://github.com/kkapsner/CanvasBlocker/issues/425). All of them were resolved or I had do close them because I did not get an answer for my following up questions that I have to prompt to solve the issue.
I do not say that Panopticlick does not maintain accurate results. I simply say that some people try to solve the problem in the last 10 years and made progress (the most know is the TOR Browser and the Firefox uplift privacy.resistFingerprinting). I know that CanvasBlocker is not perfect and there will be other fingerprinting techniques and attack vectors in the future that CB does not cover at the moment. But at the moment (and especially with the Canvas hashes on Panopticlick) it's working fine.
The "random number generator" is a setting withing the CanvasBlocker settings - I could show you a screenshot of where to find it if we were on Github...
It is set to "persistent" if you selected the "stealth" preset upon installation.
I do not see a point why Mozilla would want to buy my add-on. If they would want to incorporate it into their browser they simply could to it as it's open source and the licence allows the usage for non commercial usage (and they do charge money for Firefox). There are loads of good add-ons that work and that are not integrated into Firefox. That's the idea and beauty of Firefox: you can customize it.
393 reviews
- Rated 5 out of 5by ColorNewb, 6 days ago
- Rated 1 out of 5by jenustar5, 22 days agothe cloudflare issue reappeared and more. now only works when setting exception in general --> block mode --> challenges.cloudflare.com = block only blacklist
or when disable the addon in all addons menu.
even when disable the addon for the site by addon icon does not work. only rule above.
can this be fixed?? or is the addon become useless if cf updates like this it can then track you?
sorry for review I try github but it does not show the post when log of so shadow ban?? - Rated 5 out of 5by Firefox user 18446095, a month ago
- Rated 2 out of 5by Firefox user 14059926, a month agoHas started to suddenly break a lot of websites, even while I have done no configuration changes in years. What's interesting that sites are broken even after disabling CanvasBlocker on a specific website (using the icon in the extension menu), only working once the entire extension is disabled. An example is a Grafana instance on the local network that I thought was a server-side issue, but was caused by CanvasBlocker (even while it was disabled for the domain).
- Rated 5 out of 5by kingrose, a month ago
- Rated 3 out of 5by Firefox user 18415085, a month agoI love this extension, but it is breaking Linkedin right now. There is an issue open on github already, are there plans to fix this issue in the upcoming weeks?
- Rated 4 out of 5by abdoun, a month ago
- Rated 5 out of 5by volker01, a month ago
- Rated 5 out of 5by Firefox user 18408000, 2 months ago
- Rated 5 out of 5by Firefox user 18368977, 2 months ago
- Rated 5 out of 5by Nero, 2 months agoFunktioniert einwandfrei. Ist dass Add-On sinnvoll, wenn man privacy.resistFingerprint aktiv hat (about:config) ?
Developer response
posted 2 months agoJa, es bietet weitere Funktionalitäten. Siehe https://github.com/arkenfox/user.js/issues/767 und https://github.com/kkapsner/CanvasBlocker/issues/158 - Rated 4 out of 5by Firefox user 18383988, 2 months agoOverall works well BUT, when protecting Navigator (choosing a different OS or browser, any of the 2) it is caught by https://iphey.com/
Developer response
posted 2 months agoNavigator protection is always tricky and you cannot hide it completely. But if I choose a different OS it does not get caught by this page. Maybe there is something additional that causes that in your setup. Developer response
posted 2 months agoPlease open an issue at https://github.com/kkapsner/CanvasBlocker/issues with your details. This should not happen and I do not see a massive memory consumption.- Rated 5 out of 5by Firefox user 18252931, 3 months ago
Developer response
posted 3 months agoPlease revert to version 1.9 - version 1.10.1 is in the works.
See https://github.com/kkapsner/CanvasBlocker/issues/699 and https://github.com/kkapsner/CanvasBlocker/issues/700 for the progress of the solution.- Rated 5 out of 5by Tiger, 3 months ago
- Rated 3 out of 5by emotwink, 4 months agoThis particular extension draws too much power from my laptop. Otherwise it is working incredibly well.
- Rated 5 out of 5by Zodd, 5 months ago
- Rated 5 out of 5by folgoris, 5 months ago
- Rated 4 out of 5by snadge, 5 months agonot perfect, but it helps, especially if it is used with other addons, it still doesn't randomize your fingerprint like BRAVE does, only BRAVE gets 3 yes's on EFF's 'cover your tracks' (Ads, Trackers, Fingerprints), or, this addon, with Ublock Origin, Privacy Badger, Local CDN and NoScript (is what I use on Librewolf) gets you all 3 yes's on EFF (1 in 900, so 'common as muck' fingerprint, and unable to track & trace through fingerprinting)
- Rated 5 out of 5by Firefox user 18264023, 5 months ago
- Rated 5 out of 5by Leland359, 6 months ago