ProxyJump does not behave as ProxyCommand #1629
-
Checklist
ConfigurationBlink Shell Version: Testflight v16.0.2.617 Describe the bugConnecting to a remote host using ProxyJump does not work but using ProxyCommand does work. The login is by using password and the usernames through the different bastions is also different. I experience the same behavior when using When configured with ProxyCommand, it does work and the verbose output removes the Expected behaviorI can login to the remote host using ProxyJump as using ProxyCommand. Blink Verbose Output
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Thanks a lot for your report. I'm not able to replicate this. As you noticed, ProxyJump is just a translation to ProxyCommand, but devil is in the details here. Maybe what is going on is that when you use ProxyCommand, you are doing that translation yourself so you are passing everything properly but not with ProxyJump. One thing I have noticed:
I think this should actually be: First you connect to the Proxy, and instruct it to create a stdio tunnel to remotehost, and remotehost is "Remotehost" for the Proxy. So you have them the flipped. If you send the Host configuration we may be able to help further. |
Beta Was this translation helpful? Give feedback.
Thanks a lot for your report. I'm not able to replicate this. As you noticed, ProxyJump is just a translation to ProxyCommand, but devil is in the details here. Maybe what is going on is that when you use ProxyCommand, you are doing that translation yourself so you are passing everything properly but not with ProxyJump. One thing I have noticed:
'ssh -W [url from proxyhost]:22 remotehost'
I think this should actually be:
'ssh -W [url from remotehost]:22 proxyhost'
First you connect to the Proxy, and instruct it to create a stdio tunnel to remotehost, and remotehost is "Remotehost" for the Proxy. So you have them the flipped. If you send the Host configuration we may be able to help further.