microsoft / microsoft/vscode-remote-release
SSH explorer can't determine user from match block
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
1Password's SSH Bookmarks feature creates SSH config entries that look like this:
# 1Password Item: wo-mac
Match Host wo-mac.taila0f8a.ts.net User user
IdentitiesOnly yes
IdentityFile ~/.ssh/1Password/SHA256_Oec5X91ZYb6AkJnsW83vMmYsTy2dDRvWqygTkMoBsQE.pub
The SSH remote explorer in VS Code does not detect the configured user "user", and using the remote explorer to connect fails because SSH can't determine which key to use just from the host - the match block isn't satisfied, so it doesn't get the instruction to use a particular IdentityFile.
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
Start with the SSH remote explorer's handling of SSH configuration and compare host-only lookup with the shown Match Host ... User block. Trace how the configured user and IdentityFile are selected, then verify that the explorer can connect using this configuration rather than failing to satisfy the match block.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- devtools, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100