svn commit: r279603 - in head: bin/rcp usr.bin/rlogin usr.bin/rsh

[Slawa Olhovchenkov]

On Thu, Mar 05, 2015 at 02:20:59PM +0000, David Chisnall wrote:

> On 5 Mar 2015, at 14:13, Slawa Olhovchenkov <slw at zxy.spb.ru> wrote:
> > 
> > Not better, no.
> 
> Does telnet support creating server sockets?  No.  

don't need for me.

> Does telnet support IPsec?  No.

Let me guess, only from root and only when kernel with IPsec?
And this is equalent to setkey?

> Does telnet let you specify the tcp window size? No.

tcp window size?
not see in manual. Do you talk about "-I length Specifies the size of
the TCP receive buffer."? This is not tcp window size. And for TCP you
can't specify the tcp window size -- this is dynamic value.

> Does telnet come with a massive selection of options for insecure login / authentication?  Yes.

This is may right to use or not to use secure or not secure login /
authentication.
Also, I am use telnet login for check kerberos authentication (ssh
kerberos authentication (SSO) broken 10 years ago. nobody care).

> Telnet is a tool for insecure remote access.  nc is a tool for creating and debugging socket connections.
> 
> > telnet more verbose (and by default and more).
> 
> 'nc -v' is less to type than 'telnet' and provides *more* debugging support via -D.

% nc -v -D zxy.spb.ru 81
nc: connect to zxy.spb.ru port 81 (tcp) failed: Connection refused
% telnet zxy.spb.ru 81
Trying 195.70.199.98...
telnet: connect to address 195.70.199.98: Connection refused
telnet: Unable to connect to remote host

telnet talk about used IP address.
nc -D don't talk any additional info.

> > And what about 'tools, not policy'?
> 
> What about it?  We provide a tool that *is designed for creating and
> debugging sockets*.  You instead want a tool for insecure remote
> login that happens to sort-of work for creating and debugging
> sockets and your justification for wanting it is that you can use it
> for debugging sockets.

I am can use one tool for insecure login, for secure login and for
test network sockets. Why not?

> From your previous posts, you've clearly not read the nc man page
> and have absolutely no idea what it is capable of.  Why not spent

I am use telnet more 20+ years. I am don't need change telnet to nc
for my purpose.

> five minutes learning about the tool that we provide that is
> *designed specifically for your requirements* and then suggest
> places where it could be improved for your needs, rather than
> insisting that we provide you with a hammer so that you can keep
> bashing screws into walls?

You are sell me tools that I am don't need.
I can use telnet in any condition, I am reflexive use telnet.
When I am need to use nc -- I will use nc.
Don't force me to use nc, please!