Re: Possible error message bug in nmap-4.11 on Gentoo

[Peter Oven <myintended () gmail com>]

I have discovered that specifying a list scan instead of a ping scan will also 
produce the same result.  Linux 2.4.29 (Slackware 10.1)


root@kurtz:~# nmap -sL -p1-1024 192.168.1.5

Starting Nmap 4.20ALPHA8 ( http://Insecure.Org ) at 2006-10-12 09:56 PDT
No ports specified -- If you really don't want to scan any ports use ping scan...
QUITTING!
root@kurtz:~# nmap -sP -p1-1024 192.168.1.5

Starting Nmap 4.20ALPHA8 ( http://Insecure.Org ) at 2006-10-12 09:56 PDT
No ports specified -- If you really don't want to scan any ports use ping scan...
QUITTING!
root@kurtz:~#


Peter Oven

Mike Wallette wrote:
> Hello!
>
> While running nmap against a host on my internal network today, I specified a pair of mutually incompatible options 
> by mistake.  nmap displayed an error message and terminated without running the scan, as it should, but the error 
> message returned didn't quite match the problem:
>
> $ sudo nmap -sP -v -v -v -p1-1024 192.168.3.62
>
> Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2006-10-11 09:36 AKDT
> No ports specified -- If you really don't want to scan any ports use ping scan...
> QUITTING!
> $
>
> As you can see, I *was* using a ping scan, and I *did* specify ports.  Of course, that was the problem--you shouldn't 
> specify ports when running a ping scan.  Not a big problem, but I thought I would point it out, in case you'd like to 
> fix it.
>
> Here is the relevant system information regarding the host from which I was running the scan:
>
> $ uname -a
> Linux 2.6.17-gentoo-r8 #1 SMP PREEMPT Wed Sep 20 15:51:03 AKDT 2006 i686 Genuine Intel(R) CPU           T2600  @ 
> 2.16GHz GNU/Linux
> $ sudo nmap -V
>
> Nmap version 4.11 ( http://www.insecure.org/nmap/ )
> $
>
> Sincerely,
>
> Michael Wallette
> mike () gecko-ak org

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