security-and-privacy/CanvasBlocker
security-and-privacy/CanvasBlocker
1
0
Fork 0
mirror of https://github.com/kkapsner/CanvasBlocker synced 2024-12-23 05:10:27 +01:00
Code Releases Activity
CanvasBlocker/.documentation/faq/permissions.md
kkapsner 7cfc43194a Text corrections/improvements.
2020-03-22 14:25:15 +01:00

1.1 KiB
Raw Blame History

Why does CanvasBlocker need permission X?

Here is the list of permission that CanvasBlocker needs and the reason why it's needed:

  • <all_urls> and tabs: CanvasBlocker needs to be able to interact with all possible urls and tabs as fingerprinting attempts could be done everywhere.
  • storage: to store the settings the storage.local API is used.
  • webRequest and webRequestBlocking: to insert the CSR headers in a request in order to protect the data-URLs. Once this bug has been fixed I can completely remove the data-URI protection (see here for further information).
  • contextualIdentities and cookies: for support of browser containers. I would like to make this optional for only the people that use containers but I cannot (see here for further information).
  • privacy: this permission is needed to read if the user has privacy.resistFingerprinting enabled. A notice about a slightly changed behaviour of CanvasBlocker is displayed in the settings page in that case.