mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #751] Why does floccus require https://*/ instead of activeTab permission? #480
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#480
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @krsch on GitHub (Dec 24, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/751
Is your feature request related to a problem? Please describe.
I think giving an extension permission to access and modify data on all pages greatly increases a possible attack surface: a vulnerability in any of the extensions gives an attacker just too much access.
Describe the solution you'd like
Web extensions allows a developer to specify the
activeTabpermission. As MDN puts it "If an extension has the activeTab permission, then when the user interacts with the extension, the extension is granted extra privileges for the active tab only." Chrome store considers this permission harmless enough to hide it when showing extension permissions.Describe alternatives you've considered
Another alternative is to remove
https://*/permission. I don't see how floccus uses it.Additional context
activeTabpermission is described on MDN and Chrome Developers@marcelklehr commented on GitHub (Dec 31, 2020):
See the README section on permissions
@krsch commented on GitHub (Jan 1, 2021):
Sorry, didn't find it README. Isn't it possible switch to Permission API and runtime permissions?
@marcelklehr commented on GitHub (Jan 1, 2021):
That's a good idea. I'll look into that, once the current issues have been resolved.
@github-actions[bot] commented on GitHub (Mar 21, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.