[ On Fri, January 22, 1999 at 08:44:30 (EST), Jeffrey Altman wrote: ]
> Subject: Re: How do I sz/rz under an ssh connection?
>
> > > I can and has been for many years.
> > >
> > > SET HOST * <port>
> >
> > Hmm... I didn't know about this, and it's not given as an example in
> > the on-line help. I was looking for a command-line option on C-Kermit
> > to tell it to listen on a specified port (presumably in "server" mode),
> > but I didn't see one....
>
> All commands can be issued on the command line with the -C "<command list>"
> option.
Sure, but that still didn't help me in my quest to find some way to get
kermit to listen for a TCP/IP connection on a given local TCP port.
> > > SET HOST <host> <port>
> >
> > It should be possible then to tunnel a kermit connection through SSH,
> > though I've never set SSH tunnels up, so I don't have a cook-book
> > example of how this might be done...
>
> Right. But if 'ssh' did not require the controlling process to be a
> PTY I could simply say:
>
> SET NETWORK TYPE COMMAND
> SET HOST ssh host
>
> But because 'ssh' requires that the controlling process be a PTY for
> it to make a terminal connection this does not work.
That's not what I was thinking.
There should be no need for kermit to provide a controlling process for
SSH if you use an SSH tunnel.
Assume I've set up an SSH connection to a remote host, and I've told SSH
to forward any connections to local port 22222 through to the remote
port 11111.
I should then be able to set up a kermit server process listening on
port 11111 on the remote system:
kermit
> set host * 11111
server
(of course I won't see the prompt and the entry to server mode until a
connection is completed, but that's OK as it seems to at least accept
type-ahead -- all that's missing is some scripting to re-start the
listen after a connection closes so that you can use as many kermit
sessions as you want until you interrupt the kermit server script)
Then on the local system I need only type "kermit -j localhost:22222 -s
file*" and a connection should be forwarded through SSH to the waiting
kermit process on the other end and all the "file*" files should be
transferred.
(I haven't yet figured out how to get SSH to do this -- ssh doesn't
forward the port in the way I expected, but it should merely be a matter
of getting all the command-line arguments right. Neither do I know if
this is possible on non-Unix hosts, nor do I care, especially since this
is just an academic exercise to prove it can be done -- nobody needs to
do it because SSH already provides a more than adequate file transfer,
and remote process connection, facility.)
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <robohack!woods>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
