Bewertungen für CanvasBlocker
CanvasBlocker von kkapsner
Bewertungen von ezekielk
Bewertet mit 1 von 5 Sternen
von ezekielk, vor 5 JahrenAfter installing this add-on, Panopticlick's test shows I have zilch protection from fingerprinting. The author claims that the unique fingerprint is different each time you test it, but that's just not true...almost everything remains unchanged. Most alarming: also true for both hash numbers.
Edit: Responding to your comment: I have tested via Panopticlick many times, reloading the page, or opening a new page and testing again. I get no difference from one test to another, including the two hash numbers, which always remain the same. Shuffling people off to Github's CanvasBlocker issues is not the answer! I've tried another fingerprint hider that is also highly rated (Antifingerprint), and likewise it doesn't work. According to EFF, there is no solution yet...and is why they don't recommend any anti-fingerprint add-on, nor have made their own. And they're pretty much the last word re. online security. See:
https://www.eff.org/press/mentions/2010/11/30-0
People are just fooling themselves if they think any anti-fingerprint add-on really works.
Edit 2: I'm not interested in reporting to Github, I doubt anything will be done about it, as I am not the only person who gets failed protection with CanvasBlocker. Opening a ticket with Github would be like plunking a message down a bottomless, black pit. Panopticlick may be 10 years old, but it still maintains accurate results...what is there to update? I have privacy.resistFingerprinting set to "false," BTW...though I did have it on "true" for awhile. Doesn't seem to make any difference with Panopticlick. As for "persistent random number generator enabled," there is no such option in about:config. My point is this: if your add-on actually worked, Mozilla would've made you rich by purchasing the rights to embed it in their browser.
Edit: Responding to your comment: I have tested via Panopticlick many times, reloading the page, or opening a new page and testing again. I get no difference from one test to another, including the two hash numbers, which always remain the same. Shuffling people off to Github's CanvasBlocker issues is not the answer! I've tried another fingerprint hider that is also highly rated (Antifingerprint), and likewise it doesn't work. According to EFF, there is no solution yet...and is why they don't recommend any anti-fingerprint add-on, nor have made their own. And they're pretty much the last word re. online security. See:
https://www.eff.org/press/mentions/2010/11/30-0
People are just fooling themselves if they think any anti-fingerprint add-on really works.
Edit 2: I'm not interested in reporting to Github, I doubt anything will be done about it, as I am not the only person who gets failed protection with CanvasBlocker. Opening a ticket with Github would be like plunking a message down a bottomless, black pit. Panopticlick may be 10 years old, but it still maintains accurate results...what is there to update? I have privacy.resistFingerprinting set to "false," BTW...though I did have it on "true" for awhile. Doesn't seem to make any difference with Panopticlick. As for "persistent random number generator enabled," there is no such option in about:config. My point is this: if your add-on actually worked, Mozilla would've made you rich by purchasing the rights to embed it in their browser.
Antwort des Entwicklers
geschrieben am vor 5 JahrenThe 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.
397 Bewertungen
- Bewertet mit 4 von 5 Sternenvon newmomizi (JP), vor 5 Tagenウェブサイトが全く正常に動作しないことはほとんどありませんが、一部のウェブサイトでは非常に動作が遅くなることがあります。
性能の低いコンピュータでこれを使用するのはおすすめしません。 - Bewertet mit 5 von 5 Sternenvon Moejoe, vor 6 TagenUnderrated extension, everyone who values privacy should use it.
- Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 13194197, vor 25 Tagen
- Bewertet mit 5 von 5 Sternenvon Krisna S. Putra, vor einem Monat
- Bewertet mit 5 von 5 Sternenvon ColorNewb, vor einem Monat
- Bewertet mit 1 von 5 Sternenvon jenustar5, vor 2 Monatenthe 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?? - Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 18446095, vor 2 Monaten
- Bewertet mit 2 von 5 Sternenvon Firefox-Benutzer 14059926, vor 2 MonatenHas 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).
- Bewertet mit 5 von 5 Sternenvon kingrose, vor 2 Monaten
- Bewertet mit 3 von 5 Sternenvon Firefox-Benutzer 18415085, vor 2 MonatenI 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?
- Bewertet mit 4 von 5 Sternenvon abdoun, vor 2 Monaten
- Bewertet mit 5 von 5 Sternenvon volker01, vor 2 Monaten
- Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 18368977, vor 3 Monaten
- Bewertet mit 5 von 5 Sternenvon Nero, vor 3 MonatenFunktioniert einwandfrei. Ist dass Add-On sinnvoll, wenn man privacy.resistFingerprint aktiv hat (about:config) ?
Antwort des Entwicklers
geschrieben am vor 3 MonatenJa, es bietet weitere Funktionalitäten. Siehe https://github.com/arkenfox/user.js/issues/767 und https://github.com/kkapsner/CanvasBlocker/issues/158 - Bewertet mit 4 von 5 Sternenvon Firefox-Benutzer 18383988, vor 3 MonatenOverall works well BUT, when protecting Navigator (choosing a different OS or browser, any of the 2) it is caught by https://iphey.com/
Antwort des Entwicklers
geschrieben am vor 3 MonatenNavigator 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. - Bewertet mit 2 von 5 Sternenvon ValorBalorbus, vor 3 MonatenSometimes consumes up to 100 megabytes memory.
Antwort des Entwicklers
geschrieben am vor 3 MonatenPlease 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. - Bewertet mit 5 von 5 Sternenvon Firefox-Benutzer 18252931, vor 4 Monaten
Antwort des Entwicklers
geschrieben am vor 4 MonatenPlease 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.- Bewertet mit 5 von 5 Sternenvon Tiger, vor 4 Monaten
- Bewertet mit 3 von 5 Sternenvon emotwink, vor 5 MonatenThis particular extension draws too much power from my laptop. Otherwise it is working incredibly well.
- Bewertet mit 5 von 5 Sternenvon Zodd, vor 6 Monaten