228 reviews
  • Where can i test the success of CanvasBlocker?

    Does it make problems with twitter header image upload?
    i got probs
    You can go to http://kkapsner.github.io/CanvasBlocker/test/test.html and check if the displayed hash changes on every reload.

    I know of no problems with twitter. But if you think that it is CB related please open an issue at https://github.com/kkapsner/CanvasBlocker/issues - there we can communicate much better.
  • Doesn't make my canvas fingerprint less unique. amiunique.org still tells me that my similarity ratio is below 0.1% which means I have a very unique canvas fingerprint.
    In the default settings the canvas fingerprint is changed on every page reload (you can test that on http://kkapsner.github.io/CanvasBlocker/test/test.html). Yes - this makes the fingerprint unique but since it is not constant you cannot be tracked.

    If you want further information/discussion please open an issue on https://github.com/kkapsner/CanvasBlocker/issues where we can communicate nmuch easier.

    PS: similar issue on github: https://github.com/kkapsner/CanvasBlocker/issues/154
  • Thank you for this extension (and for keeping it opensource). Nowadays it's getting harder and harder to get a sense of real privacy. CanvasBlocker + AdGuard for Windows + Privacy Badger + HTTPS Everywhere + custom user.js helps me feel safer on a growing data collection frenzy.
    You're welcome.
  • Please provide a reason why you gave one star. Maybe I can fix the issue or improve CB with your input.
  • Does not work according to fingerprint test at https://panopticlick.eff.org/
    What do you mean with "does not work"? Please open an issue at https://github.com/kkapsner/CanvasBlocker/issues where we can communicate better and therefore I can help better.
  • 100% unique mean that is not really natural, canvas should not be unique but changed in order to be natural.
    Unique canvas fingerprints will do much worse.
    Is like you said you have a device that never exist.

    To better understand how this work :
    Google already have a full database with all kind of canvas signatures from all worldwide devices (iphone, android, computers, etc...), and if your canvas signature will not match on them database then you fail, it is a prove that your canvas is fake. If you try to spoof the signature then image pixel parameters will not match and again you fail so is almoust imposible to pass canvas.

    On default settings may make it pass the google test.

    For example google will not ask for SMS confirmation when a new gmail account is created because he trust the device you use.

    Most of people must understand why unique signatures is bad practice and all softwares that spoof parameters will make traking services to detect the device much easy
    Please open an issue at https://github.com/kkapsner/CanvasBlocker/issues where we can discuss this. AMOs rating comments are too limited to have a good conversation.

    One small comment on unique signatures: they are not bad by itself as long as they are not persistend (i.e. the timestamp you connect to the server is very likely to be a unique signature but it's not persistent). This is the case in the CB default settings.
  • Works Fine
  • It's doing it's job
  • Excellent.
  • Can't seem to get version 0.4.4b working with Firefox ESR 52.7.2, there's just no icon visible anywhere on the UI.

    Edit: My bad! I remember that this addon had an icon before but nowadays it hasn't. Works great!
    This Addon does not have an icon that is always visible. Only a fingerprint icon is displayed in the adress bar when some canvas data was faked for the web page. You can test at http://kkapsner.github.io/CanvasBlocker/test/test.html

    If you still think that it's not working properly try version 0.4.4a and open a new issue at https://github.com/kkapsner/CanvasBlocker/issues

    EDIT: no problem. Glad that it works for you.
  • Keep up the good work and thank you.
  • Not good. Had partial protection before installing add-on. This add-on makes my browser 100% unique.
    Yes, in the standard settings of CB the fingerprint that is produced with CB is quite unique but not persistent. That means the browser itself (and therefore you) cannot be indentified by it. (The same issue was reportet on github: https://github.com/kkapsner/CanvasBlocker/issues/154 - if you want further informations you can explore the issues there or post a new one.)

    Also there are a lot of options which change the behaviour of CB (just mark the expert mode). If you want a less unique fingerprint you can use the "white" random number generator which will result in fingerprints similar to those of the Tor browser.
  • Hey there, take a look at Browser Console to know about your add-on's error. Keep up a good work.
    I do not see any errors. Please open an issue at https://github.com/kkapsner/CanvasBlocker/issues where you can describe the scenario when you see the errors.
  • Perfect!!! Thanks!!!