microsoft / microsoft/vscode-remote-release
[Remote-SSH Bug]: Directives in config files that are included are erroneously case-sensitive
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Is there an existing issue for this bug?
- I have searched the existing issues
Required Troubleshooting Steps
- I have followed these troubleshooting steps
- I have tried both values of the
remote.SSH.useLocalServersetting
Connect Locally
It connects successfully
->
No response
Expected Behavior
VS Code seems to be case sensitive when parsing SSH config files that are included by the main config file. Specifically, it seems to recognize only Host directives but not HOST or host. According to the ssh_config spec, directives are case-insensitive. And indeed, HOST and host seem to work properly when put in the main config file.
Steps To Reproduce
- In the
~/.ssh/configfile add the line
Include test.config
- Make file
~/.ssh/test.configwith contents
HOST test
USER test
The host test does not appear in the Remote Explorer after refreshing it. However, replacing HOST -> Host and USER -> User makes the host appear.
Remote-SSH Log
Remote-SSH Log
Only file saving operations in the log, nothing relevant.
Anything else?
No response
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
Reproduce with ~/.ssh/config including test.config, using lowercase or uppercase HOST and USER directives, then refresh the Remote Explorer. Start by tracing how the included file is parsed, while checking both values of remote.SSH.useLocalServer. Done means included directives are treated case-insensitively and the test host appears consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100