microsoft / microsoft/vscode-remote-release

Remote SSH Extension - Disable File(s) Download from server option

Open
#10,488 7 comments 17 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

feature-request ssh
Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

This has been requested twice: https://github.com/microsoft/vscode-remote-release/issues/7106 and https://github.com/microsoft/vscode-remote-release/issues/7534.

We need an option to disable this:
Image

We need to be able to view the files from within VSCode but not allow their download. This is useful in a variety of cases for data protection. Copy-paste of text/code is always possible, but in many cases the files accessible via SSH aren't limited to text (see my screenshot) and for those the only option to "copy" is download.

Quoting this comment from a previous raising of this issue:

Removing this option does not eliminate code leaks but makes it much more time consuming, difficult and it adds some protection to leaking code bases or ML algorithms in our case, allows us to work more remotely securely / onboard ad-hoc developers that may not have company restricted laptops and it avoids easily allowing them to copy entire code bases locally.

Therefore, this is the third time this feature request is made but due to the time limit of 60 days it always gets closed before it collects the required number of upvotes (see here and here):

🙁 In the last 60 days, this feature request has received less than 10 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Can we please raise attention as this is an important feature for many workflows? Also considering that it was raised twice already before this issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.