security-and-privacy/CanvasBlocker
security-and-privacy
/
CanvasBlocker
mirror of https://github.com/kkapsner/CanvasBlocker
1
0
Fork 0
Code Releases Activity
153 Commits 81 Branches 113 Tags 12 MiB
JavaScript 87.4%
HTML 6%
CSS 4.1%
PHP 2.5%
Go to file
kkapsner 2c5bd5824b Changes for release submission 2017-02-01 11:50:37 +01:00
addon description Documentation cleanup. 2017-02-01 11:48:05 +01:00
data Switch from frameScript to require("sdk/remote/..."). 2017-01-31 21:51:08 +01:00
doc Initial Commit 2014-07-31 03:05:51 +02:00
lib window objects of <frame>s with no url do get the "about:blank" too late -> treat blank URL the same way. 2017-02-01 11:15:05 +01:00
locale Version 0.3.6 2016-12-17 10:50:24 +01:00
test Improved test page. 2017-01-31 20:59:57 +01:00
.gitattributes 💥🐫 Added .gitattributes 2014-07-31 03:04:18 +02:00
.gitignore First beta 2014-08-05 14:36:05 +02:00
.jpmignore Added button in options site to display release notes. 2016-11-13 15:34:33 +01:00
AllowIcon.png Separated invisible and visible canvas asking 2014-08-17 23:32:23 +02:00
AskIcon.png Separated invisible and visible canvas asking 2014-08-17 23:32:23 +02:00
Icon.png First beta 2014-08-05 14:36:05 +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
Settings.png Next version number (0.1.5) 2014-12-16 11:37:45 +01:00
canvasblocker.xpi Changes for release submission 2017-02-01 11:50:37 +01:00
locales.json Switch to jpm. 2016-01-29 00:07:41 +01:00
package.json Changes for release submission 2017-02-01 11:50:37 +01:00
releaseNotes.txt Documentation cleanup. 2017-02-01 11:48:05 +01: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.