`Host *` blocks overwritten in SSH config files, leading to disconnects

[ericpaulsen]

a large customer identified an issue where our VS Code extension overwrites Host * entries in SSH configs, instead of respecting them (coder config-ssh does this here).

There's a Host * block in our default SSH config and the VSCode plugin was putting it's blocks after those. It seemed as those even after moving the blocks around, the plugin would remove the blocks and place them at the end of the file.

We have a sample config file that includes empty comment markers for coder's config-ssh and VS Code blocks above a Host *. config-ssh obeys the placement but VS Code does not.

this line of code is where the Host * block is appended to the end of the config file: https://github.com/coder/vscode-coder/blob/main/src/sshConfig.ts#L188

the customer confirmed that commenting out the Host * block did resolve the issue.

First we tried just moving the Host * to the end of the file, but that got moved right back on the next connection. Eventually I just told them to comment out that block, which isn't ideal

[ericpaulsen]

to compare, OpenSSH searches the file from top to bottom and uses the parameter from the first block that matches, so if there's a block earlier in the file that has a parameter that's also in the VSCode block, it'll use the earlier block's parameter:

Host *
  foo star

Host vscode
  foo vscode
  bar vscode

this shakes out to be {foo: star, bar: vscode}