security-and-privacy/CanvasBlocker
security-and-privacy
/
CanvasBlocker
mirror of https://github.com/kkapsner/CanvasBlocker
1
0
Fork 0
Code Releases Activity
274 Commits 81 Branches 113 Tags 12 MiB
JavaScript 87.4%
HTML 6%
CSS 4.1%
PHP 2.5%
Go to file
kkapsner ae0763cfe6 Improved design of the page action display. 2017-10-14 12:24:53 +02:00
.documentation Improved design of the page action display. 2017-10-14 12:24:53 +02:00
.vscode Added vscode tasks for the web-ext tool. 2017-10-07 23:14:53 +02:00
_locales Cleanup of page action interface. 2017-10-03 12:17:14 +02:00
icons Improved design of the page action display. 2017-10-14 12:24:53 +02:00
lib getImageData does not need to be faked in input mode when facing a non 2d context. 2017-10-12 00:25:12 +02:00
options Code cleanup. 2017-10-05 19:00:00 +02:00
pageAction Improved design of the page action display. 2017-10-14 12:24:53 +02:00
test Extended standard test to capture additional iframe scenarios. 2017-10-10 20:33:42 +02:00
.eslintrc.json Simplified require and further linting. 2017-10-06 16:06:31 +02:00
.gitattributes 💥🐫 Added .gitattributes 2014-07-31 03:04:18 +02:00
.gitignore Changed printed icon to right size. 2017-09-17 01:23:55 +02:00
LICENSE.txt Added MPL 2015-01-16 13:05:40 +01:00
README.md Updated release notes and readme. 2017-09-24 00:06:03 +02:00
manifest.json Version 0.4.1 2017-10-06 23:01:34 +02:00
releaseNotes.txt Improved design of the page action display. 2017-10-14 12:24:53 +02:00

README.md

This add-on allows users to prevent websites from using the Javascript <canvas> API to fingerprint them. Users can choose to block the <canvas> API entirely on some or all websites (which may break some websites) or just block or fake its fingerprinting-friendly readout API. More information on <canvas> fingerprinting can be found at http://www.browserleaks.com/canvas.

The different block modes are:

  • block readout API: All websites not on the white list or black list can use the <canvas> API to display something on the page, but the readout API is not allowed to return values to the website.
  • fake readout API: Canvas Blocker's default setting, and my favorite! All websites not on the white list or black list can use the <canvas> API to display something on the page, but the readout API is forced to return a new random value each time it is called.
  • fake at input: on display of text the drawn pixels get modified slightly. This makes the detection of the add-on harder but is less secure. On WebGL-canvas the behaviour is identical to "fake readout API".
  • ask for readout API permission: All websites not on the white list or black list can use the <canvas> API to display something on the page, but the user will be asked if the website should be allowed to use the readout API each time it is called.
  • block everything: Ignore all lists and block the <canvas> API on all websites.
  • allow only white list: Only websites in the white list are allowed to use the <canvas> API.
  • ask for permission: If a website is not listed on the white list or black list, the user will be asked if the website should be allowed to use the <canvas> API each time it is called.
  • block only black list: Block the <canvas> API only for websites on the black list.
  • allow everything: Ignore all lists and allow the <canvas> API on all websites.

Special thanks to:

  • spodermenpls for finding all the typos
  • Thorin-Oakenpants for the icon idea