IssueRaiser

[Feature Request] Extension Permissions, Security Sandboxing & Update Management Proposal

I believe that Visual Studio Code should support some kind of "Extension Permission Management", complete with prompts, warnings, opt-in, and opt-out, similar to what has been supported for some time now with Chrome, Firefox, and other browsers. # Reference Screenshot I've provided, for reference, some screenshots showing Extension Permission and update prompts and management UIs in the below screenshot, as well as others torwards the end of this proposal. #### Chrome prompting to approve additional permissions when updating an extension: ![image](https://user-images.githubusercontent.com/4053734/41503578-cfbf9ee4-718c-11e8-82c8-8a97fb8b61a7.png) _(See additional screenshots at the very bottom.)_ # Scope and Benefits I have proposed, in detail here, how Extension Permissions management could function and be exposed to users, including descriptions of dialogs for prompting users to allow/deny permissions on extension install vs. updating, changes to Extensions Sidebar and Extension Details Marketplace pages, grouping/managing extensions by Category/Collection in VSCode, specific warnings and when to show them, types of permissions could define (and whether may default to opt-out or opt-in for them), APIs could provide, how extensions could operate with more limited or conditional functionality, and how could crowdsource extension safety reporting. I'm also proposing that users can disable Auto-Update behavior for specific extensions, which, besides being useful in its

Posted by PowerWeb5 on Jun 17, 2018, 2:11 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments

support (Other)

[Feature Request] Extension Permissions, Security Sandboxing & Update Management Proposal

PowerWeb5Jun 17, 2018, 2:11 AM

I believe that Visual Studio Code should support some kind of "Extension Permission Management", complete with prompts, warnings, opt-in, and opt-out, similar to what has been supported for some time now with Chrome, Firefox, and other browsers. # Reference Screenshot I've provided, for reference, some screenshots showing Extension Permission and update prompts and management UIs in the below screenshot, as well as others torwards the end of this proposal. #### Chrome prompting to approve additional permissions when updating an extension: ![image](https://user-images.githubusercontent.com/4053734/41503578-cfbf9ee4-718c-11e8-82c8-8a97fb8b61a7.png) _(See additional screenshots at the very bottom.)_ # Scope and Benefits I have proposed, in detail here, how Extension Permissions management could function and be exposed to users, including descriptions of dialogs for prompting users to allow/deny permissions on extension install vs. updating, changes to Extensions Sidebar and Extension Details Marketplace pages, grouping/managing extensions by Category/Collection in VSCode, specific warnings and when to show them, types of permissions could define (and whether may default to opt-out or opt-in for them), APIs could provide, how extensions could operate with more limited or conditional functionality, and how could crowdsource extension safety reporting. I'm also proposing that users can disable Auto-Update behavior for specific extensions, which, besides being useful in its

Comments (0)

No comments yet. Start the discussion.

Comment on this issue