VSCode SSH Agent的安全与资源消耗问题
问题概述
The post and its comments express concerns about the security implications of VSCode's SSH agent, the large storage footprint of the remote .vscode-server (e.g., 6 GB), and the complexity of shipping binaries over SSH, which may expose the local machine to remote compromise and cause user unease.
痛点标签
- 远程代理可能对本地机器造成安全风险
- 远程 .vscode-server 占用大量存储空间
- 通过 SSH 隧道传输二进制文件的复杂性与不确定性
待验证问题
- 您是否担心远程代理能够访问本地文件系统并执行任意命令？
- 您是否能接受在远程机器上占用数 GB 的存储空间？
- 是否需要更细粒度的权限控制来限制代理的功能？
证据
原话 · @Anonymous
Missing a (2025)FYI VSCode's SSH Agent is a godsend for remote development - the "disadvantages" that Fly lists are part of its advantages. I've worked in several teams that have made extensive use of the extension, and it's never been an issue. You can restrict SSH access arbitrarily to ensure whatever security or access guardrails you need.
原话 · @Anonymous
2026-09-24 09:35:24 dev ~ du -h -d 0 .vscode-server 6.0G .vscode-server This is what makes it bananas for me. I don't know what Microsoft is thinking if they allow this.
原话 · @Anonymous
This part of VSCode's architecture is acceptable to me. The reverse direction, where a compromised remote can do whatever it wants to my local machine, is not.
原话 · @Anonymous
The agent is supposed to run on a remote dev box. The purpose is to make the remote machine an extension of your local one, to run extensions, containers, install packages, test deployments, forward ports and tons more. Tunneling is part of the feature set. If you are installing it on production servers and are surprised by its behavior that’s on you.
免责声明：本卡片由 AI 从社区讨论中提炼，属于「痛点证据」，是需求分析与验证的起点，不等同于「已验证的市场需求」。AI 存在分析局限，关键决策前请打开上方原始讨论人工复核。