security-and-privacy/CanvasBlocker
security-and-privacy
/
CanvasBlocker
mirror of https://github.com/kkapsner/CanvasBlocker
1
0
Fork 0
Code Releases Activity
229 Commits 81 Branches 113 Tags 12 MiB
JavaScript 87.4%
HTML 6%
CSS 4.1%
PHP 2.5%
Go to file
kkapsner e0e226d3f0 Changed printed icon to right size. 2017-09-17 01:23:55 +02:00
.documentation Updates settings screenshot. 2017-07-16 00:12:51 +02:00
_locales Typos. 2017-08-12 16:48:30 +02:00
icons Changed printed icon to right size. 2017-09-17 01:23:55 +02:00
lib Made readPixels consistent with the other faked readout functions. 2017-08-13 23:41:57 +02:00
options Add fakeAlphaChannel to options page. 2017-08-13 23:30:16 +02:00
pageAction Added logging lib with setting to control log level. 2017-07-27 19:14:04 +02:00
test Test cleanup. 2017-08-13 23:44: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 Documentation cleanup. 2017-02-01 11:48:05 +01:00
manifest.json Added svg icons 2017-09-16 16:18:19 +02:00
releaseNotes.txt Typos. 2017-08-12 16:48:30 +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.