Recensioni per CanvasBlocker
CanvasBlocker di kkapsner
Recensione di ezekielk
Valutata 1 su 5
di ezekielk, 5 anni faAfter 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.
Replica dello sviluppatore
pubblicato il 5 anni faThe 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.
419 recensioni
Replica dello sviluppatore
pubblicato il 6 giorni faPlease open an issue at https://github.com/kkapsner/CanvasBlocker/issues to describe your issues with captchas.- Valutata 5 su 5di Ugarov, 10 giorni fa
Replica dello sviluppatore
pubblicato il 14 giorni faA unique fingerprint is not a bad thing if it changes: https://canvasblocker.kkapsner.de/faq/#uniqueFingerprint- Valutata 2 su 5di blackSP, 15 giorni faChecked before and after installing/activating this extension trying all profiles and see zero improvement in my identification score on several fingerprinting sites like coveryourtracks.eff.org and amiunique.org. Benefit of the doubt after reading dev's comment that it works anyway. Can't find any proof of that though.
Replica dello sviluppatore
pubblicato il 14 giorni faYou need to check the details of the fingerprinting sites. Depending on your settings you can have a unique fingerprint - but this is not a bad thing if it changes: https://canvasblocker.kkapsner.de/faq/#uniqueFingerprint - Valutata 5 su 5di Utente Firefox 17902463, 18 giorni fa
- Valutata 5 su 5di CyberV99, 23 giorni fa
- Valutata 5 su 5di FFReviewAccount, un mese faHelps stop sites and corporations from tracking your internet activity. It works with no issues.
Replica dello sviluppatore
pubblicato il un mese faPlease check if the solution in https://github.com/kkapsner/CanvasBlocker/issues/734#issuecomment-2549927939 solves your problem. If not please comment on this issue with your CanvasBlocker settings so I can investigate.- Valutata 5 su 5di RazorCMV, 2 mesi fa
- Valutata 5 su 5di Utente Firefox 12097049, 2 mesi fa
- Valutata 5 su 5di Szaboo Ferenc, 3 mesi fa
- Valutata 5 su 5di Jonah, 4 mesi fa
- Valutata 5 su 5di Utente Firefox 18602700, 4 mesi fa
- Valutata 4 su 5di celever.boy, 4 mesi faon canvasblocker.kkapsner.de/test/test.html this add-on change everythings except "offscreen Worker Test" the value always same after refresh and causes they still track you. i hope developer fix it
Replica dello sviluppatore
pubblicato il un mese faUnfortunately the workers do not offer an API to interact with them from a web extension. That's why I opened https://bugzilla.mozilla.org/show_bug.cgi?id=1636977.
So I do not see a maintainable way to handle this issue. (The only would be to disable workers...) - Valutata 5 su 5di Utente Firefox 18605300, 4 mesi fa
- Valutata 4 su 5di zeblur, 4 mesi fa
- Valutata 5 su 5di Shefour, 5 mesi fa
- Valutata 5 su 5di Aaaa, 5 mesi fa
- Valutata 5 su 5di Utente Firefox 18555038, 5 mesi fa
- Valutata 4 su 5di Andre Bell, 5 mesi faDamages Linkedin, as other comments here and on github have noted. Enable 'Advanced' settings and add Linkedin.com to the whitelist and all is well again. Do NOT alter any other settings unless you want your browser vulnerable to the noted exploit mentioned in the FAQ.
- Valutata 5 su 5di Rint Fint, 6 mesi fa
- Valutata 2 su 5di TELLALL4ALL, 6 mesi fa8-31-24: slows down and blocks some pages from loading-alerts from browser that CB is fucking up your connection
produces frequent error" canvas blocker is slowing down your browser, stop it?"
browser and or webpage issues warning that this extension is slowing down your browser do you want to stop it?