Revisiones de Canvas Defender
Canvas Defender por Multilogin
15 revisiones
- Se valoró con 1 de 5por Hex (🐦: @hex), el hace 2 mesesThis used to be an essential part of my toolkit for privacy on the web, but now generating new canvas noise doesn't change the signature on the test at BrowserLeaks, so I guess it no longer works.
https://browserleaks.com/canvas
By contrast, Firefox's own anti-fingerprinting protection (available since Firefox 120) does work when enabled, although it takes a browser restart to get a new signature on the test. - Se valoró con 1 de 5por Whetsit Tuya, el hace 6 mesesit doesn't let you disable its tremendously abrasive notifications
- Se valoró con 1 de 5por Usuario de Firefox 14301971, el hace un año
- Se valoró con 1 de 5por yenaskithegar, el hace 3 añosWhen i found out that fsf.com tries to fingerprint me, i know there is something going on in this add on. Take too much memory, target overreach, bunch of ui for psychological effect
- Se valoró con 1 de 5por KING, el hace 5 añosDoes not work, https://www.deviceinfo.me/, shows canvas as allowed, not spoofed or blocked.
- Se valoró con 1 de 5por daniel.mota.leite, el hace 5 añosDidn't work for me, maybe there is something else blocking it (umatrix, privacy badger), but with this installed and without, the test site show the same fingerprint
- Se valoró con 1 de 5por zingmars, el hace 5 añosWhile the idea is nice theoretically, practically this addon isn't all that useful. Apps using canvas for legitimate reasons (i.e. WhatsApp web file upload, draw.io file export) will often have coloured tint (or sometimes it will just break the app completely) on them, which not only affects the web experience, but will also make you trackable. The addon does have a white-list function, but I haven't been able to get it to work. There's also an annoying notification that pops up on every webpage that tries to read your canvas hash and you can't actually disable it.
- Se valoró con 1 de 5por pedz, el hace 6 años
- Se valoró con 1 de 5por 田生, el hace 6 añosIt claimed to be a better solution than "Canvas fingerprint blocking tactics" in its artical. But indeed, it is very easy to be detected. By drawing a large gray (#666) block and read its content, browsers without this extension installed will report all pixels are gray. But with this extension, You would get a green / red / blue or some other colored pixels. And by testing the changing of colors, website may simply know a user is using this extension. As the result, this extension won't be better than a canvas fingerprint blocking tool as it claimed. While there are more users using tools to block a fingerprint (as a built-in of Tor browser), using this extension would be even a worse idea.
Respuesta del desarrollador
publicado el hace 6 añosThe article you mentioned was written almost 2.5 years ago. Since then new technologies emerged and we also wrote additional articles clarifying questions around canvas fingerprinting.
We also work on perspective technologies for protection from canvas fingerprinting, see a video presentation here https://www.youtube.com/watch?v=xSTFf-xKmE0 - Se valoró con 1 de 5por Usuario de Firefox 14082665, el hace 6 años
- Se valoró con 1 de 5por BRW, el hace 6 añosNot working with gmail on Firefox Linux 57.0.3 (64-bit). Gmail loads about 3/4's of the way on load bar and stops. With Canvas Defender disabled, gmail loads ok.
- Se valoró con 1 de 5por Usuario de Firefox 13167162, el hace 7 añosWas a real PIA troubleshooting all my extensions to see which one was making gmail unusable. You would think the dev would at a minimum test compatibility with gmail.
- Se valoró con 1 de 5por Bob Smith, el hace 7 añosIn use without issue since v1.0.6 (5 Stars!), 1.1.0 breaks google and several web sites so far. Need to whitelist mail.google.com, drive.google.com, etc. (merely google.com doesn't work). And bankofamerica.com as one example. It's too tedious to figure out a site needs it and then entering it manually. Reverting to 1.0.9. Thank you.
- Se valoró con 1 de 5por sonabe, el hace 7 añosgot error:
Current canvas noise hash
#
Last changed: (Scheduled change: )
did not show # and canvas.