Josh Spicer

The initial upstream (https://github.com/cyjake/ssh-config/issues/84) has been closed. I opened https://github.com/cyjake/ssh-config/issues/89 to ask a follow up

This should be fixed in tomorrow's pre-release build of the extension. If you have a sec, please let me know then if it helps

Testing: The fix was a major update to the upstream parsing package. Confirm that both this bug is fixed and that your existing config is continuing to work as expected.

numerous open issues related for SSH: https://github.com/microsoft/vscode-remote-release/issues/5927#issuecomment-2542472315, https://github.com/microsoft/vscode-remote-release/issues/9090, https://github.com/microsoft/vscode-remote-release/issues/9454

~~Working on a solution here: https://github.com/microsoft/vscode/pull/238815~~

We have a fallback mechanism now for when `--install-extension` is used on server launch, but for whatever reason the extension fails to install. In my testing (where I _deny_ access...

I have followed the reproduction steps and can no longer repo. We made some changes to SSH_AUTH_SOCK in the second half of this year that likely helped this scenario. I...

Thank you for taking the time to open an issue. Could you please share your logs (`> Remote-SSH: Show Log` in the command palette) after reproducing the issue? Does it...

That said, to support unique configurations it seems logical to provide a setting. In this case the issue is not in the SSH extension, but in the VS Code Remote...

@flying-sheep you could use the command shown below to manually install an extension you've copied to your remote machine On a host that can download extension, you'd find them by...