PaulDotCom mailing list archives

dealing with nmap XML and NSE output

From: dimitrios at gmail.com (Dimitrios Kapsalis)
Date: Tue, 1 Jun 2010 10:42:24 -0500

I suppose, one could through together an XSLT program which can pull the
relevant information from the xml file and create an HTML report for
example.

Another option would be to use a streaming API such as SAX to parse the xml
file and pull the relavant information your looking to use.

On Tue, Jun 1, 2010 at 9:03 AM, Mike Patterson <mike at snowcrash.ca> wrote:

Ruby has a nice module for dealing with nmap xml output.  It's the only
one I found that handles --script type output at all, much less
gracefully.  Currently I've only used it for simple things like helping
to get SSL certificate vendors and expiry dates (guess what part of my
job is), but I could clean it up a bit and send it along if anybody's
interested.

The gem is nmap-parser.

Mike
_______________________________________________
Pauldotcom mailing list
Pauldotcom at mail.pauldotcom.com
http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom
Main Web Site: http://pauldotcom.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.pauldotcom.com/pipermail/pauldotcom/attachments/20100601/3c6459d4/attachment.htm

Current thread:

dealing with nmap XML and NSE output Chris Teodorski (May 31)
- dealing with nmap XML and NSE output Ron (May 31)
  - Message not available
    - dealing with nmap XML and NSE output Chris Teodorski (Jun 01)
- dealing with nmap XML and NSE output Dan McGinn-Combs (Jun 01)
- <Possible follow-ups>
- dealing with nmap XML and NSE output Jim Halfpenny (Jun 01)
- dealing with nmap XML and NSE output Cody Dumont (Jun 01)
  - dealing with nmap XML and NSE output Mike Patterson (Jun 01)
    - dealing with nmap XML and NSE output Dimitrios Kapsalis (Jun 01)