> 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.
Here is the relevant description from the nc README file:
" If netcat is compiled with -DTELNET, the -t argument enables it
to respond to telnet option negotiation [always in the negative,
i.e. DONT or WONT]. This allows it to connect to a telnetd and get
past the initial negotiation far enough to get a login prompt from
the server. Since this feature has the potential to modify the
data stream, it is not enabled by default. You have to understand
why you might need this and turn on the #define yourself. "
You see, it does telnet negotiations- purely for the purpose of getting
through to the other side- without the intention of supporting ANYTHING.
> I have some experience handling telnet negotiations, I have even written
> a tiny and simple telnet client that behaved somewhat well with telnet
> servers. I could add such functionality to the `nc' also if you wish.
>
> Other thing, could you add nc to hand all rest arguments to the command
> started with `-e' option. That would ease some things, for example line...
>
> /usr/bin/nc -vv -n -t -l -p 23 -e /usr/bin/ile /bin/ash -i
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.
-Tom
