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

【vsix Completeness】How can VSCode protect the .vsix from Maliciously replacement? #104288

Closed
caozhaohong opened this issue Aug 8, 2020 · 2 comments
Assignees
Labels
marketplace Microsoft VS Code Marketplace issues

Comments

@caozhaohong
Copy link

  • VSCode Version:
  • OS Version:

Steps to Reproduce:

Does this issue occur when all extensions are disabled?: Yes/No

Dear team:

Thank u let us engoyed a perfect tool.

I want to know something, about following publishing of .vsix:
https://code.visualstudio.com/api/working-with-extensions/publishing-extension

Question: How can our VS Code Extension Marketplace avoid following case happen?

Case 1: developer 1 published ExtensionA but hacker replaced his 'ExtensionA' with a 'Fake ExtensionA'? And other developments downlaod a 'ExtensionA' but infact it is made by hacker, instead of developer 1 .

Further more, it is possible that we can learn more about VSCode Extension Marketplace security detail.

Thanks.

@sandy081
Copy link
Member

sandy081 commented Aug 9, 2020

Seems to be a Marketplace question but assigning to you (@joaomoreno) if there are any insights from VSCE side.

@sandy081 sandy081 added the marketplace Microsoft VS Code Marketplace issues label Aug 9, 2020
@joaomoreno
Copy link
Member

The Marketplace enforces authentication for publishing extensions, so the hacker would need access to the developer's credentails.

@github-actions github-actions bot locked and limited conversation to collaborators Oct 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
marketplace Microsoft VS Code Marketplace issues
Projects
None yet
Development

No branches or pull requests

3 participants