You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the reason might be this: Jumpserver acts as an SSH proxy. When users connect, they're actually connecting to Jumpserver first, which then forwards the connection to the target server. Because of this, the returned information might be processed by Jumpserver, making it different from directly connecting to sshd.
The text was updated successfully, but these errors were encountered:
To get the original JumpServer functionality of SSH, you can also try to create a Custom SSH Connection in XPipe. There you can specify all necessary SSH config options, e.g. ProxyJump to use jump servers as you would with the SSH CLI.
I think the reason might be this: Jumpserver acts as an SSH proxy. When users connect, they're actually connecting to Jumpserver first, which then forwards the connection to the target server. Because of this, the returned information might be processed by Jumpserver, making it different from directly connecting to sshd.
The text was updated successfully, but these errors were encountered: