Nmap Development: silly -p bug

[Arturo 'Buanzo' Busleiman <buanzo () buanzo com ar>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

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?


- --
Arturo "Buanzo" Busleiman
Independent Linux and Security Consultant - SANS - OISSG - OWASP
http://www.buanzo.com.ar/pro/eng.html
Mailing List Archives at http://archiver.mailfighter.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI54XNAlpOsGhXcE0RCozMAJ9M3B9wIO7eqY7ETtR45dI6khh+qACdEs9c
arhMXnqG09IOYUwpHhZrGBU=
=0WFa
-----END PGP SIGNATURE-----

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