-
Notifications
You must be signed in to change notification settings - Fork 349
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
8.0.2 new permissions #2210
Comments
Seems to be related to #2157 |
Please consider making these permissions optional as with bookmarks. |
It's not just about privacy (the goal of this extension), but also about security. The extension and Firefox itself could have bugs, which could (and will) be exploited by malicious actors. |
I also think the rationale for new permissions should at least be explained somewhere. Maybe in the dedicated wiki page? |
Indeed, I'm fairly sure #2157 is the reason: the new permissions are needed to allow per-container VPN use. I've pinged some people about updating the wiki page and release notes, but given that it's Thanksgiving in the US today, it might take a while for folks to respond. |
Seconded on explaining the permission and making them optional. The first time I've been irritated using this add-on, which is generally good, is that it is asking for permissions there is no obvious reason it needs with no explanation. This is both a security and privacy risk. I expect it is rerlated to VPN access, which seems like a good feature, but absolutely one that should be optional. Personally, I think it should be mandatory for apps/add-ons to provide some explanation for why they need permissions (not just Firefox add-ons, but, e.g. Android apps), so I think explanation should always be provided for anything that isn't obvious. |
Agree with the above. Permissions should always be justified and when possible, optional. |
I think the feature of being able to choose which interface is used per container is fantastic. Not to get too in the weeds (and speaking without having looked at how you've planned on implementing it), there should also either be a per container DNS setting or a notice to the user that firefox will use whatever the default DNS setting is on the host (e..g. /etc/resolv.conf). |
still holding off on accepting the new permissions, would have been quite helpful indeed if it was revealed which other programs Firefox MAC plans to share data with. |
In fairness, if you Cancel (instead of Learn more): – then you have release notes, which don't offer a detailed explanation but did announce per-container integration with something other than the extension (after which, a change to permissions did not surprise me):
More broadly: |
WHY should everyone be forced to accept the new permissions for a service they may not use? Nobody not subscribed to the VPN service should ever be forced to weaken their security by accepting permissions that do not add any functionality for them. MAKE THESE PERMISSIONS OPTIONAL. |
Apart from that, this release causes delays when loading websites. |
@swentel Maybe report that in a new issue. |
Thanks for these comments! I agree with you. We will work on making these permissions optional. This will be done as soon as possible. |
The permissions page was updated. Thank you. |
Version 8.0.2 of the extension is requesting new permissions.
I hope the permissions page will be updated to explain why the new permissions are required.
https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/versions/
https://github.com/mozilla/multi-account-containers/wiki/Permissions
The text was updated successfully, but these errors were encountered: