Remote session fails to connect with ProxyJump

[bymet]

Issue Type: Bug

1. Add ssh config file with next structure

Host jump
  User <jump-user-name>
  HostName <jump-ip-address>

Host server
  User <user-name>
  HostName <ip-address>
  ProxyJump jump

2. Select server throught VSCode-Inseder UI
3. Get next error message

Can't connect to server: unreachable or not Linux x86_64 (posix_spawn: No such file or directory)

Extension version: 0.37.0
VS Code version: Code - Insiders 1.35.0-insider (a5536b8f5a16a10d859f3dec1e59701671bf069e, 2019-05-20T05:17:36.269Z)
OS version: Windows_NT x64 10.0.17763
Remote OS version: Linux x64 4.4.0-17763-Microsoft

System Info

Item	Value
CPUs	Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz (4 x 3912)
GPU Status	2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: enabled surface_synchronization: enabled_on video_decode: enabled webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	15.89GB (5.15GB free)
Process Argv
Screen Reader	no
VM	0%

Item	Value
Remote	WSL
OS	Linux x64 4.4.0-17763-Microsoft
CPUs	Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz (4 x 3900)
Memory (System)	15.89GB (5.15GB free)
VM	0%

[roblourens]

Can you share the log from the "Remote - SSH" output channel?

[bymet]

Confirming that mobyedge-server is a valid reachable host
Running type "C:\Users\STANIS~1.TES\AppData\Local\Temp\vscode-linux-multi-line-command-mobyedge-server.sh" | ssh  mobyedge-server to confirm the host platform
> 
> Pseudo-terminal will not be allocated because stdin is not a terminal.
> CreateProcessW failed error:2
> posix_spawn: No such file or directory
> 
"uname" terminal command done
mobyedge-server: unreachable or not Linux x86_64. (posix_spawn: No such file or directory)

[bymet]

Also forgot to mention that same ssh configuration works fine inside WSL

[roblourens]

And if you type ssh mobyedge-server in a command prompt, that works? Is it possible that ssh is not on your path in vscode?

[bymet]

It works fine inside bash/WSL, but fails inside powershell/cmd with next message

CreateProcessW failed error:2
posix_spawn: No such file or directory

[bymet]

Looks like some thing wrong with ssh itself on windows

[roblourens]

Oh, it sounds like linux ssh is on your path, not windows ssh.

[roblourens]

I think this is a duplicate of #359 then.

[pd93]

@roblourens. I don't think this is a dupl. of #359. This happens to me when the only installed version of OpenSSH is the Powershell one.

I'm fairly sure it is however, a dupl. of #18. I would appreciate if you could take a look at the comments over there. I believe this may be caused by PowerShell/Win32-OpenSSH#1172, which has been open for quite some time. This seems like a pretty big limitation of SSH in Windows.

[bymet]

@roblourens, Recently I installed next version of ssh. Right now everything works fine. So yes, looks like it's issue with ssh itself.

[roblourens]

Thanks for bringing PowerShell/Win32-OpenSSH#1172 to my attention. That does sound like a serious issue.