Support for ProxyCommand (-o) #1622
thinkOfaNumber
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
Hm, I looked at forking the project but all the proxy connectors expect a TCP socket, so I guess the only way to make it work is put another layer in front of the proxy executable and serve it via a local socket, I can't just simply create a new proxy type that handles executables... |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Has anyone used SSH.NET with a ProxyCommand? It's much like a HTTP proxy from what I can tell except it works by redirecting SSH IO via stdin/stdout pipes to the given command, rather than over a HTTP connection.
ProxyCommand can be any executable that is able to pass the data back & forth. e.g. Azure ARC allows connection to firewalled machines via SSH but you need to go through a ProxyCommand, which (I think) sends it over service bus. This works with OpenSSH:
ssh -o ProxyCommand="sshProxy_windows_amd64_1_3_017634.exe -r relay-info-file" user@host
where "host" is not contactable on the internet. This proxy command and relay file can be setup by an az command, so the only step is to get SSH.NET to send IO to the command rather than over a HTTP Proxy, as far as I can tell.
It would be great to know if anyone else has tried proxy commands in any of the forks or PRs, but I couldn't find it. The closes I found was a jump host, but that's an SSH-listening jump box and not the same thing.
Beta Was this translation helpful? Give feedback.
All reactions