Re: ncat 5.10BETA handling of -l -p is not compatible with nc-1.10

[Ron <ron () skullsecurity net>]

On 01/11/2010 04:05 PM, David Fifield wrote:
> I committed the code to make -p set the listen port. I also made it an
> error if you try to give more than one port, like
>         ncat -l 80 443
>         ncat -l -p 80 443
> I don't know what to print as a warning. "You don't need the -p with
> Ncat"? It makes me think of Google's "Save time by hitting the return
> key instead of clicking on the search button."
>
> David Fifield

On a related note, while the topic is open: are there any other places 
that ncat and nc diverge that could potentially cause incompatibilities?
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/