tunneling through stdin/stdout, source routing

John Davidorff Pell johnpell at gmail.com
Tue Nov 14 11:14:10 EST 2006

couldn't some carefully constructed host directives in the config  
file do this?

host cookie
	hostname monster
	ProxyCommand ssh -t -l ralph monster ssh -t -l root cookie



On Nov 11, 2006, at 4:30 AM, Simon Richter wrote:

> Hi,
> quite often I find myself using commands like
> $ ssh foo nc bar 12345
> to connect to another host behind a firewall, and I also have a lot of
> these commands in my ssh config file. Since this relies on the server
> having netcat available (which a lot don't, or in some really old
> version that will not shut down properly) it breaks often, and I  
> wonder
> whether it would make sense to have an option in the ssh client that
> told it to connect to the server, then open a tunneled connection and
> connect that to stdin/stdout.
> As an extension, there could also be a source routing option in the
> config file that would take care of setting up a chain of ssh
> connections if I need multiple hops.
> As far as I can see this requires no special support from the  
> server, so
> should be easy to implement; I'm not sure though how I would go about
> implementing such a thing in OpenSSH because of the development model
> that would effectively require me to run OpenBSD to test my patches
> before submitting them.
> Any ideas?
>    Simon
> _______________________________________________
> openssh-unix-dev mailing list
> openssh-unix-dev at mindrot.org
> http://lists.mindrot.org/mailman/listinfo/openssh-unix-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2520 bytes
Desc: not available
Url : http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20061113/a2f97256/attachment.bin 

More information about the openssh-unix-dev mailing list