Steve Dodd <[EMAIL PROTECTED]> writes:
>
> Uh, but AFAICS ssh doesn't have anything like telnet's linemode, which was
> the point of my message. Character-at-a-time editing sucks when the link
> latency is ~100ms.
SSH has a port-forwarding mode whereby an arbitrary TCP/IP socket
connection can be piggybacked over the secure connection. Given how
incredibly useful this feature is, I'm surprised it seems to be so
little known and used.
In short, the following should do the trick:
ssh -f -L 2323:localhost:23 remotehost sleep 60
telnet localhost 2323
The "-f" puts "ssh" in the background while the "-L" argument listens
on local port 2323 (or any other unused port of your choice). When a
connection is made to that local port, the traffic is forwarded
bidirectionally, transparently, and encryptionally (!) to the
remotehost's "localhost port 23" (i.e., the Telnet service on the
remote host).
The "sleep 60" is an arbitrary command. It just can't complete before
the first connection to local port 2323.
Kevin <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
