mailing list archives
Re: [BUG] Nmap host specification parsing
From: David Fifield <david () bamsoftware com>
Date: Sun, 14 Jun 2009 11:13:56 -0600
On Sun, Jun 14, 2009 at 03:43:12AM +0300, ithilgore wrote:
It applies to the latest svn version and the problem is that when
you put an extra comma ',' after any host, then Nmap adds an
additional target to the list. The target is the IP that corresponds
to 0 for the least significant byte and for the rest of the bytes to
the same class network as the host before the comma.
$ nmap -sL -n 10.0.0.1, 10.0.0.2
Starting Nmap 4.85BETA10 ( http://nmap.org ) at 2009-06-14 03:33 EEST
Host 10.0.0.1 not scanned
Host 10.0.0.0 not scanned
Host 10.0.0.2 not scanned
Nmap done: 3 IP addresses (0 hosts up) scanned in 0.00 seconds
I found some other undocumented syntax supported by Nmap a while ago.
We talked about having Nmap use the Ncat code a little bit, because the
Ncat code has tests and fewer quirks. Ncat's addrset code doesn't
support host enumeration, but there's nothing in the design to keep that
from being implemented.
So if it helps, you could use the Ncat code in Ncrack, or just port the
Ncat code into TargetGroup.
Sent through the nmap-dev mailing list
Archived at http://SecLists.Org