Support for ProxyJump in .ssh/config
Version: 1.0.170 Platform: macOS x64 21.2.0 Plugins: none Frontend: xterm-webgl
In my ssh/config file, I have something like:
Host my.serverurl.com HostName my.internalname.com ProxyJump my.proxyname.com
However, if I try to connect to my.serverurl.com in a new tab I get the following error:
X my.serverul.com: jump host "openssh-config:my.proxyname.com" not found in your config
Would it please be possible to support ProxyJump in tabby? Thank you and keep up the good work
Some progress.
If I change the ssh/config file to include a separate Host section for the ProxyJump, like this:
Host my.proxyname.com
HostName my.proxyurl.com
Host my.serverurl.com
HostName my.internalname.com
ProxyJump my.proxyname.com
Then it attempts to connect. Notice that the ProxyJump name must still have the format of an URL: It cannot be, for example:
Host proxy
HostName my.proxyurl.com
Host my.serverurl.com
HostName my.internalname.com
ProxyJump proxy
Or Tabby will complain. Unfortunately, it is still not working completely. I don't use ssh-agent, so it should ask for my password twice: once for the proxy and once for the final machine. Tabby does this, but the second password always fails with the following error:
SSH Connecting to <hidden>
SSH Host key fingerprint:
SSH SHA256 <hidden>
SSH Keyboard-interactive auth requested:
X All configured authentication methods failed
X Not connected
Slowly getting there. I can't wait to solve this and make Tabby my daily driver!
However, since I don't use ssh-agent, ssh should ask me for two passwords, one for the proxy and one for the final machine.
To add to this, config entries that don't have the full hostname next to 'Host' don't even work. For example, the following won't even work (which is honestly a bit confounding):
Host home
HostName home.myhost.com
The only way to make it work is to change it to:
Host home.myhost.com
Fixed hostname parsing - but could you please double check that authentication works if you create both profiles manually in Tabby?
I downloaded the latest nightly and I can confirm that this issue has indeed been fixed. I also tried manually creating both profiles in Tabby and it appears to work fine as well. Do note that I am not the individual who created this issue but I suspect they will have the same results as I did since we both were experiencing the same exact issue.
I apologize for the huge delay in reporting: the hostname parsing works, but the authentication still gives me exactly the same error as before (this is with version alpha 174 on MacOS)
Any progress on that? Jump host are not working