microsoft / microsoft/vscode-remote-release
Disable executables installed over SSH
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Type: Bug
I connected to a remote server over SSH so I can browse files and run SSH commands in the termnal. It works well.
However shortly after I noticed that node was consuming several GB of RAM and swapping to disk (I only have 1GB). Also I don't have Node.js installed.
VS Code should never be installing things without my permission. I just want to browse the filesystem and use the terminal. This does not need a whole Node.js installation. Is there no way to disable this?
Extension version: 0.120.0
VS Code version: Code 1.106.3 (bf9252a2fb45be6893dd8870c0bf37e2e1766d61, 2025-11-25T22:28:18.024Z)
OS version: Darwin arm64 24.6.0
Modes:
Remote OS version: Linux x64 6.12.58-gentoo
System Info
| Item | Value |
|---|---|
| CPUs | Apple M4 Max (16 x 2400) |
| GPU Status | 2d_canvas: enabled direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: enabled_on trees_in_viz: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | 1, 1, 1 |
| Memory (System) | 128.00GB (1.15GB free) |
| Process Argv | --crash-reporter-id d0d24dbf-e443-4bf0-aa9b-bc68a67cdae1 |
| Screen Reader | no |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | SSH: tkmizparty-dev.awwright.name |
| OS | Linux x64 6.12.58-gentoo |
| CPUs | AMD EPYC-Genoa Processor (1 x 0) |
| Memory (System) | 0.94GB (0.35GB free) |
| VM | 0% |
A/B Experiments
vsliv368:30146709
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
aj953862:31281341
nes-set-on:31340697
6abeh943:31336334
envsactivate1:31353494
cloudbuttont:31379625
todos-1:31405332
qwen_all_req:31402696
3efgi100_wstrepl:31403338
trigger-command-fix:31379601
auto_model_enabled:31385282
use-responses-api:31390855
anonusage:31403420
ec5jj548:31422691
terminalsuggestenabled:31426255
cp_cls_c_966_ss:31426491
defaultvisibility:31426295
expandedtokens:31426297
c0683394:31419495
478ah919:31426797
7gj03587:31426750
a5gib710:31426782
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are identified in the report. Start by reproducing the SSH connection on a low-memory remote Linux host and identify which component installs and runs node. Done means the behavior is understood and users have a reliable way to prevent unwanted executable installation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100