This also breaks the web, resulting in major confusion.

Searching the web for netcat linux howto or tutorial returns almost 100%
broken examples.

Netcat fails without any hint of why, while saying the flags you used where 
valid.
using man nc does does not solve this confusion.
>From 'man nc'
>  -l      Used to specify that nc should listen for an incoming connection 
> rather than initiate a connection to a
>          remote host.  It is an error to use this option in conjunction with 
> the -p, -s, or -z options.  Additionally,
>          any timeouts specified with the -w option are ignored.

This does not say you specify the port with -l port 
Instead it says how not to use it. Not much help.

I propose the following changes

1. Change short usage message to include ref to the man page and the date of 
switch of behaviour
 - nc usage flags where changed %date%. Use man nc for more information.

2. Remove the "It is a n error" (way too strong, suggests that this will
result in some kind of damage) and at the end (of each parameter) say
"can not be used with -p" etc.

3. Add information on HOW -l is used. -l port. See "-i interval" and
compare the two. -i has a parameter. -l does not.

Sounds good?

Regards,

Torbjorn

-- 
broken version of netcat installed by default
https://bugs.launchpad.net/bugs/590925
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to