Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Access to history permission #12

Open
2 tasks
DanAtkinson opened this issue May 13, 2019 · 1 comment
Open
2 tasks

Access to history permission #12

DanAtkinson opened this issue May 13, 2019 · 1 comment

Comments

@DanAtkinson
Copy link

Summary

Steps to reproduce

(Please provide detail steps).

Ensure you have v2.1.0

What is the current bug behaviour?

(What actually happens).

I am asked if I wish to allow the extension access to my entire browser history.

What is the expected correct behaviour?

(What you should see instead).

A VPN extension should not concern itself with my browser history.

Relevant logs and/or screenshots

Possible fixes suggested remediation

Remove the requirement for the browser history permission to be given, as there is no explanation for it in the changelog and, as per your recent reviews it seems that others have a problem with it as well.

Assignees and labels

( please add labels as applicable )
~bug ~confirmed
~feature ~suggestion
~Windows ~Linux ~OSX
~Emergency ~Major ~Minor
%"milestone"
/cc @dev /assign @tester

  • Patched
  • Verified patch
@taesup
Copy link
Contributor

taesup commented May 20, 2019

This has been fixed in the latest release (2.1.1) where we removed the "tabs" permission that caused that error to the "activeTab" permission that allows the same functionality but without the warning. The only use of the "activeTab" permission within the extension is to pre-populate the current tab's url into the Bypass List Tile on the main extension view.

Apologies for any issues this might have caused.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants