Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

"Read your browsing history" permission #67

Closed
philcluff opened this issue Dec 12, 2022 · 1 comment
Closed

"Read your browsing history" permission #67

philcluff opened this issue Dec 12, 2022 · 1 comment

Comments

@philcluff
Copy link

philcluff commented Dec 12, 2022

Hey there,

When this plugin was auto-updated, it added 2 new permissions.

  1. To read data on facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion
  2. To read browsing history

The first makes sense, it's the legitimate Facebook Onion address

The second I'm a little more confused about.

Could you update README.md with information on why browsing history is required?

Thanks.

@mgziminsky
Copy link
Owner

Oh, this is chrome being somewhat misleading... I'm giving a full technical response below just for the sake of linking here for details from the README entry I'll add.


The warning is caused by the webNavigation permission, which was added to handle cleaning FB navigations that use the browser history API instead of doing a normal page navigation. The extension doesn't have access to the actual browser history, only page navigations, and not even those are accessed by the extension. The extension only accesses a specific subset of the api and only on FB domains.

The chrome warning is misleading because the permission doesn't give access to the actual browser history. Technically, this permission gives the ability to see the url of any page opened in the browser, but only in the instant that it's opened, not before, not after. Even with this permission though, it still wouldn't be able to access any history that was synced from another computer, from when the extension wasn't installed/enabled, or from anything else that wasn't a result of directly opening the page in the browser with the extension.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

2 participants