Thanks to jpomiane for sending in the patch.
I have finally had the chance to migrate this small project over to Google Code. To be honest, that was the most easiest things I have ever done. They have really made the work flow for developing and releasing code extremely easy (MUCH easier than SourceForge). With that said, all further development will be done over at Google Code.
Here is the link: http://code.google.com/p/nmap-parser/
Yeah, well I have to apologize for all the delay in releasing and fixing all the bugs that were submitted through email/sourceforge. I finally took the time to go over the new enhancements to the nmap xml output and see what I was missing. Anyways, enjoy!
– Added parsing of distance information.
– Added ignoring of taskend,taskbegin and taskprogress information.
– Added tests for nmap 4.20.
– Changed lisence to MIT.
– Fixed protocol for the service handler – a bug that always returns null
Well, I have received a LOT of emails on updates and suggestions to Nmap::Parser. Just as a general announcement, I am currently STILL finishing up my thesis for my MS Degree, so it will take a little while before I can sit back down and start programming again and going through all the emails.
So that I can track all the stuff I need to do for the next version, please make sure you go to the project page and submit Bug/Feature Request. I would appreciate it very much and I thank you for your patience
The main reason for this release is major speed improvements and reduction in memory usage. Most functions are now genereated on the fly, reducing compile time (as well as saving memory). It was one of those days when I realized I could do things better (thanks to the Cookbook). I have also updated the documentation (I had mistyped some words and function names).
I have been getting a lot of questions about this method in the new version of Nmap::Parser with
Returns an array of all the Nmap::Parser::Host objects for the scan. If the optional status is given, it will only return those hosts that match that status. The status can be any of the following: (up|down|unknown|skipped)
For those who are in the corporate world and use the Qualys (QualysGuard) vulnerability scanner, and wish to write your own applications using their API – I have created a simple connection wrapper to their API. I have uploaded this initial version to CPAN found here: http://search.cpan.org/~apersaud/Qualys-0.02/