Re: silly -p bug

[David Fifield <david () bamsoftware com>]

On Sat, Oct 04, 2008 at 12:03:41PM -0300, Arturo 'Buanzo' Busleiman wrote:
> See the port range specification very carefully:
>
> murray ~ # nmap -p 3200-3005 some_target
>
> Starting Nmap 4.76 ( http://nmap.org ) at 2008-10-04 12:01 ART
> No ports specified -- If you really don't want to scan any ports use ping scan...
> QUITTING!
>
> Ports have BEEN specified, but incorrectly. It was very quick to spot the problem (I typed 3005
> instead of 3205, thus the "range" was invalid), but as i had just compiled out of fresh svn, I first
> thought "weird, a bug, -p IS there". Maybe a clearer error message?

Thanks for the suggestion. I committed a change to make Nmap give an
error message like

Your port range 3200-3005 is backwards. Did you mean 3005-3200?
QUITTING!

David Fifield

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org