trailofbits / trailofbits/coop
ProxyJump for remote VS Code
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 243
- Forks
- 13
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 30
Description
When coop runs on a remote Linux host (e.g. SSH'd into a server), coop vscode generates an SSH config that points directly at the guest VM. VS Code on the user's laptop can't reach the guest because it's behind the remote host.
The SSH config needs a two-hop setup with a ProxyJump directive through the Linux box to reach the guest. This would allow coop vscode to work transparently when the CLI is running on a remote machine.
Expected behavior: coop vscode detects it's running on a remote host (or accepts a flag) and generates an SSH config with ProxyJump so VS Code can connect from the user's local machine through the remote host to the guest VM.
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
Locate the coop vscode entry point and the SSH config generation it uses; first inspect how the guest VM connection is currently described and whether remote-host detection or a flag already exists. Done means a remote invocation produces a two-hop config with ProxyJump through the Linux host, allowing VS Code on the user's laptop to reach the guest VM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, vscode
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100