Home page logo
/

nmap-dev logo Nmap Development mailing list archives

Re: Ignored state broken in grepable output
From: Fyodor <fyodor () insecure org>
Date: Thu, 29 May 2008 12:34:51 -0700

On Wed, May 28, 2008 at 12:59:26PM -0600, David Fifield wrote:
Hi,

I tried to reproduce the grepable output in this example:

http://nmap.org/book/output-formats-grepable-output.html#output-formats-ex-grepable-protocol-scanme

but I couldn't get it to show me the "Ignored State: closed (251)". The
problem is that Nmap's handling of multiple ignored states leaves the
ignored state as PORT_UNKNOWN when it is finished, and the grepable
output correctly sees that there are no ports in this "ignored" state,
and it doesn't print anything.

I have attached a patch that restores the output, but only in the case
that there is exactly one ignored state. I don't know what it should do
if there are more than that. I didn't test the patch against a machine
with more than one ignored state because I couldn't find one.

Looks good to me.  Since the grepable output format is deprecated, I
think it is OK that it not support multiple ignored states unless we
see demand from users that it do so.

Cheers,
-F

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


  By Date           By Thread  

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