Friday Jun 2 12:58:48 +0000 2000 Tom Oehser <[EMAIL PROTECTED]> wrote:
>
> > Your tomsrtbt nc documents to have `-t' option to handle telnet
> > negotiation, but I could not regognize any difference in operation. Is
> > there such feature or shall there be one in future.
>
> It works, I think you are expecting more than it is intended to do.
Yes, I thougth it may handle some telnet negotiations also when it acts
as a "server". Pretty dummy of me, you'd probably use that instead of
the dd trick you use now.
I thought you've done some patching to `nc' and therefore I asked...
Now that I've looked the homepage of nc and know a lot more about it
I can think what I will do next...
Currently I just wanted to get telnet client automatically go to the
character mode and not confuse the server end (shell) with some probable
telnet negotiations..
In the meanwhile I devised guite good plan to access the tomsrtbt booted
machine -- I use XEmacs 21.x and it's `ftelnet' mode. ftelnet also regognizes
a configuration variable `ftelnet-program' which by default is set to
"telnet". Changing this to `nc' eliminates the problem with telnet
negotiations. Now when I use this environment to connect to the tomsrtbt
machine (when ftelnet asks for host, the port number 23 needs always be
given also, since nc does not provide that automatically), after first
return (which works through that `dd') I can operate on that machine
guite well (command history comes from xemacs buffer, and for added value,
I get filename completion! when commands and files matches to the names
on my local machine)...
> The netcat homepage is at: http://www.l0pht.com/~weld/netcat/ which has
> links to download both the NT source and the Unix source, as well as the
> full README file (which is not distributed with tomsrtbt. Send patches,
> and try to make it turn into a smaller executable while you're at it.
.. That utility seems to be edited last sometime in 1996. Also, the code looks
a bit(!) ugly. Instead of continuing hacking w/ that code, I rather write
a totally new program which can do the following:
1) handle simple telnet (and telnetd) negotiations -- in telnetd-mode
request other end to go to character mode. In telnet-mode does simple
linemode - charactermode changes (a few gtty-stty -calls and modifying
just cbreak and echo flags of those).
2) do just transparent 2-way traffic management.
3) exec an external command (ang give rest cmd line arguments to it also),
and pass all data from network to it -- when traffic is transparent, simply
redirecting stdin and stdout of the exec'd command should be enough, and
no fork is required -- when there is telnet(d) negotiations available,
the program has to stay alive and handle the datastream until passing
it to the exec'd program. In this case fork(), and creating pipes is
required.
Probably doing this takes around a week (effective time) to complete. Would
there be any interest using such a program -- I'd imagine the size of such
a program is less than the size of `nc' -- of course some of the nc:s
functionality is missing then...
I can't promise any delivery date for this program, but if there is enough
interest I'll try to get into it very soon.
>
> -Tom
>
Tomi
