Home page logo
/

nmap-dev logo Nmap Development mailing list archives

Re: Log bogus targets in XML
From: Daniel Miller <bonsaiviking () gmail com>
Date: Fri, 4 May 2012 20:01:24 -0500

I think this is a very useful addition. Unfortunately, the entry in
the Changelog isn't being escaped on nmap.org, so it doesn't show up.
I'm not sure how important this is, but I thought I'd bring it up
anyway. http://nmap.org/changelog.html

Dan

On Fri, Apr 27, 2012 at 1:53 AM, David Fifield <david () bamsoftware com> wrote:
Currently if you give Nmap a syntactically invalid target specification
or one that can't be resolved, you get warnings like these:

$ ./nmap 1:2 3.4.5 '[6.7.8.9]'

Starting Nmap 5.61TEST5 ( http://nmap.org ) at 2012-04-26 23:51 PDT
Invalid host expression: 1:2 -- colons only allowed in IPv6 addresses, and then you need the -6 switch
Invalid target host specification: 3.4.5
Invalid character in host specification: [6.7.8.9].  Note in particular that square brackets [] are no longer 
allowed.  They were redundant and can simply be removed.

However there's no machine-readable way to see that this happened, other
than to read stderr. Here is a patch that adds this information to the
XML output in a new target element.

<target specification="1:2" status="skipped"/>
<target specification="3.4.5" status="skipped"/>
<target specification="[6.7.8.9]" status="skipped"/>

David Fifield

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


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
AlienVault