|
kathys39 has asked for the wisdom of the Perl Monks concerning the following question:
Does nmap::parser library handle the "reason" and "reson_ttl" field in an nmap xml output file?
I noticed in the new version of nmap I just downloaded - 4.68 - when a port reports that it is filtered, there is now a reason (admin-prohibited, no-response, etc). (Don't know when this was added or if it's been there a long time but I think it is very valuable for my clients) Is there a way to easly parse this element using the nmap::parser module? I can't figure out how to get this data into my db... |
Re: nmap::parser question
by Khen1950fx (Canon) on Aug 22, 2008 at 01:46 UTC
|
According to the Nmap web site, "Nmap offers no direct database output functionality". It did, however, recommend PBNJ to get your data to a database such as SQLite, MySQL, or Postgres. Looks promising---I'd give it a try. | [reply] |
|
|
Well right now I am using the nmap::parser library to parse my data and dump it into a database. I'm just curious because their doesn't seem be support for the "reason" and "reason_ttl" fields which my client wants to store....
| [reply] |
|
