Balazs Scheidler writes:
>On 29 Dec 1998, Niels [ISO-8859-1] M=F6ller wrote:
>> Command mode.
>> ssh has a somewhat limited functionality attached to its escape
>> character, by default a new-line preceeded '~'. I think it would be
>> nice if this was expanded into a command mode. From command mode, it
>> should be possible to monitor the connection, forward new ports, close
>> channels, stop forwarding ports, request key renegotiation, etc.
>
>that's a really cool idea. and emphasizing that one has to press enter
>before the escape character should really be needed. (I didn't know this
>existed until I began working on lsh) But a command-mode would be even
>more useful.
I think this would be useful too, but what the original ssh purpose was,
and I think lsh should at least be aware of, is to be compatible with the
Berkeley R* commands (rsh, rcp, rlogin). This is where the /n~ comes
from.
If you turn this into a "command" mode requiring additional
keys (ala Kermit?) you will break lots of existing scripts that might
depend on this capability (I've only ever once done such a thing, and
would never do it again, esp with perl available).
Just an FYI... You can of course make lsh into its own program and need
not be restricted by the choice of others :)
satch
==========================================================
Steve Acheson [EMAIL PROTECTED]
Cisco Corporate Information Security Cisco Systems
