<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Anthony Persaud &#187; Nmap Parser</title>
	<atom:link href="http://anthonypersaud.com/category/nmap-parser/feed/" rel="self" type="application/rss+xml" />
	<link>http://anthonypersaud.com</link>
	<description></description>
	<lastBuildDate>Mon, 19 Oct 2009 05:50:17 +0000</lastBuildDate>
	
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Nmap-Parser 1.13 Release with Servicefp support.</title>
		<link>http://anthonypersaud.com/2008/02/nmap-parser-113-release-with-servicefp-support/</link>
		<comments>http://anthonypersaud.com/2008/02/nmap-parser-113-release-with-servicefp-support/#comments</comments>
		<pubDate>Tue, 12 Feb 2008 04:51:57 +0000</pubDate>
		<dc:creator>Anthony Persaud</dc:creator>
				<category><![CDATA[Nmap Parser]]></category>

		<guid isPermaLink="false">http://nmapparser.wordpress.com/?p=25</guid>
		<description><![CDATA[Just released Nmap-Parser-1.13 with support in parsing the servicefp attribute in the service tag. This is also known as the service fingerprint. See documentation for more details.
Thanks to jpomiane for sending in the patch.
]]></description>
			<content:encoded><![CDATA[<p>Just released <a href="http://search.cpan.org/dist/Nmap-Parser/" title="Nmap Parser Module 1.13">Nmap-Parser-1.13</a> with support in parsing the servicefp attribute in the service tag. This is also known as the service fingerprint. See <a href="http://search.cpan.org/dist/Nmap-Parser/Parser.pm" title="Nmap Parser Documentation">documentation</a> for more details.</p>
<p>Thanks to jpomiane for sending in the patch.</p>
]]></content:encoded>
			<wfw:commentRss>http://anthonypersaud.com/2008/02/nmap-parser-113-release-with-servicefp-support/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Migrated project to Google Code!</title>
		<link>http://anthonypersaud.com/2007/11/migrated-project-to-google-code/</link>
		<comments>http://anthonypersaud.com/2007/11/migrated-project-to-google-code/#comments</comments>
		<pubDate>Mon, 19 Nov 2007 21:11:44 +0000</pubDate>
		<dc:creator>Anthony Persaud</dc:creator>
				<category><![CDATA[Nmap Parser]]></category>

		<guid isPermaLink="false">http://nmapparser.wordpress.com/2007/11/19/migrated-project-to-google-code/</guid>
		<description><![CDATA[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 [...]]]></description>
			<content:encoded><![CDATA[<p>I have finally had the chance to migrate this small project over to <a href="http://code.google.com/p/nmap-parser/" title="Google Code Nmap Parser">Google Code</a>. 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.</p>
<p>Here is the link: <a href="http://code.google.com/p/nmap-parser/" title="Nmap Parser Perl Module">http://code.google.com/p/nmap-parser/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://anthonypersaud.com/2007/11/migrated-project-to-google-code/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nmap-Parser 1.11 Released (yes, it&#039;s a miracle)</title>
		<link>http://anthonypersaud.com/2007/06/nmap-parser-111-released-yes-its-a-miracle/</link>
		<comments>http://anthonypersaud.com/2007/06/nmap-parser-111-released-yes-its-a-miracle/#comments</comments>
		<pubDate>Thu, 14 Jun 2007 23:17:28 +0000</pubDate>
		<dc:creator>Anthony Persaud</dc:creator>
				<category><![CDATA[Nmap Parser]]></category>

		<guid isPermaLink="false">http://nmapparser.wordpress.com/2007/06/14/nmap-parser-111-released-yes-its-a-miracle/</guid>
		<description><![CDATA[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!
Changes:
    &#8211; Added parsing of distance information.
- [...]]]></description>
			<content:encoded><![CDATA[<p>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!</p>
<p>Changes:</p>
<blockquote><p><strong>    &#8211; Added parsing of distance information.<br />
- Added ignoring of taskend,taskbegin and taskprogress information.<br />
- Added tests for nmap 4.20.<br />
- Changed lisence to MIT.<br />
- Fixed protocol for the service handler &#8211; a bug that always returns null</strong></p></blockquote>
<p><a href="http://sourceforge.net/project/showfiles.php?group_id=97509&amp;package_id=109408" title="Nmap Parser on Sourceforge latest">Nmap Parser 1.11 on SourceForge<br />
</a></p>
<p><a href="http://search.cpan.org/~apersaud/Nmap-Parser/" title="Nmap Parser on CPAN (Perl)">Nmap-Parser-1.11.tar.gz on CPAN</a></p>
<p><a href="http://sourceforge.net" title="Nmap Parser on CPAN (Perl)"><img src="http://sourceforge.net/sflogo.php?group_id=97509&amp;type=1" alt="SourceForge.net" height="31" width="88" /> </a></p>
]]></content:encoded>
			<wfw:commentRss>http://anthonypersaud.com/2007/06/nmap-parser-111-released-yes-its-a-miracle/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Will start updating as soon as&#8230;</title>
		<link>http://anthonypersaud.com/2006/05/will-start-updating-as-soon-as/</link>
		<comments>http://anthonypersaud.com/2006/05/will-start-updating-as-soon-as/#comments</comments>
		<pubDate>Wed, 10 May 2006 23:16:45 +0000</pubDate>
		<dc:creator>Anthony Persaud</dc:creator>
				<category><![CDATA[Nmap Parser]]></category>

		<guid isPermaLink="false">http://nmapparser.wordpress.com/2006/05/10/will-start-updating-as-soon-as/</guid>
		<description><![CDATA[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 [...]]]></description>
			<content:encoded><![CDATA[<p><span class="text_content">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.</p>
<p><strong>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 </strong></span></p>
]]></content:encoded>
			<wfw:commentRss>http://anthonypersaud.com/2006/05/will-start-updating-as-soon-as/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nmap-Parser 1.05 Released</title>
		<link>http://anthonypersaud.com/2005/08/nmap-parser-105-released/</link>
		<comments>http://anthonypersaud.com/2005/08/nmap-parser-105-released/#comments</comments>
		<pubDate>Sat, 13 Aug 2005 01:02:13 +0000</pubDate>
		<dc:creator>Anthony Persaud</dc:creator>
				<category><![CDATA[Nmap Parser]]></category>

		<guid isPermaLink="false">http://nmapparser.wordpress.com/2005/08/13/nmap-parser-105-released/</guid>
		<description><![CDATA[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 [...]]]></description>
			<content:encoded><![CDATA[<p>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).</p>
]]></content:encoded>
			<wfw:commentRss>http://anthonypersaud.com/2005/08/nmap-parser-105-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Where has get_host_objects() gone?</title>
		<link>http://anthonypersaud.com/2005/08/where-has-get_host_objects-gone/</link>
		<comments>http://anthonypersaud.com/2005/08/where-has-get_host_objects-gone/#comments</comments>
		<pubDate>Fri, 12 Aug 2005 01:02:04 +0000</pubDate>
		<dc:creator>Anthony Persaud</dc:creator>
				<category><![CDATA[Nmap Parser]]></category>

		<guid isPermaLink="false">http://nmapparser.wordpress.com/2007/06/13/where-has-get_host_objects-gone/</guid>
		<description><![CDATA[I have been getting a lot of questions about this method in the new version of Nmap::Parser with
all_hosts
all_hosts($status)
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&#124;down&#124;unknown&#124;skipped)
]]></description>
			<content:encoded><![CDATA[<p>I have been getting a lot of questions about this method in the new version of Nmap::Parser with</p>
<pre>all_hosts</pre>
<pre>all_hosts($status)</pre>
<p>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)</p>
]]></content:encoded>
			<wfw:commentRss>http://anthonypersaud.com/2005/08/where-has-get_host_objects-gone/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Qualys perl module for QualysGuard</title>
		<link>http://anthonypersaud.com/2005/07/qualys-perl-module-for-qualysguard/</link>
		<comments>http://anthonypersaud.com/2005/07/qualys-perl-module-for-qualysguard/#comments</comments>
		<pubDate>Wed, 27 Jul 2005 12:52:14 +0000</pubDate>
		<dc:creator>Anthony Persaud</dc:creator>
				<category><![CDATA[Nmap Parser]]></category>

		<guid isPermaLink="false">http://nmapparser.wordpress.com/2005/07/27/qualys-perl-module-for-qualysguard/</guid>
		<description><![CDATA[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 &#8211; 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/
]]></description>
			<content:encoded><![CDATA[<p>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 &#8211; I have created a simple connection wrapper to their API. I have uploaded this initial version to CPAN found here: <a href="http://search.cpan.org/~apersaud/Qualys-0.02/" title="Qualys Scanner for Perl">http://search.cpan.org/~apersaud/Qualys-0.02/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://anthonypersaud.com/2005/07/qualys-perl-module-for-qualysguard/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nmap-Parser-1.01 Released (finally)</title>
		<link>http://anthonypersaud.com/2005/07/nmap-parser-101-released-finally/</link>
		<comments>http://anthonypersaud.com/2005/07/nmap-parser-101-released-finally/#comments</comments>
		<pubDate>Mon, 04 Jul 2005 00:50:02 +0000</pubDate>
		<dc:creator>Anthony Persaud</dc:creator>
				<category><![CDATA[Nmap Parser]]></category>

		<guid isPermaLink="false">http://nmapparser.wordpress.com/2005/07/04/nmap-parser-101-released-finally/</guid>
		<description><![CDATA[After much rewriting and reworking &#8211; I am finally proud to announce that 1.01 is released. Why not 1.00? Well, I did not like my CPAN file just having a 1 by its name. Also it did pass 7 of the CPAN testers, so it should be good to go.
Please read the documentation carefully because [...]]]></description>
			<content:encoded><![CDATA[<p>After much rewriting and reworking &#8211; I am finally proud to announce that 1.01 is released. Why not 1.00? Well, I did not like my CPAN file just having a 1 by its name. Also it did pass 7 of the CPAN testers, so it should be good to go.</p>
<p>Please read the documentation carefully because there have been MAJOR changes. (If you do not want to install and have all your old script breaking). I know some people are going to get mad because of the major changes, but trust me they had to be done. In most cases, you should like the new framework.</p>
<p>Thanks for your patience and understanding. Happy 4th of July!</p>
]]></content:encoded>
			<wfw:commentRss>http://anthonypersaud.com/2005/07/nmap-parser-101-released-finally/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Nmap-Parser website up and running!</title>
		<link>http://anthonypersaud.com/2005/07/new-nmap-parser-website-up-and-running/</link>
		<comments>http://anthonypersaud.com/2005/07/new-nmap-parser-website-up-and-running/#comments</comments>
		<pubDate>Fri, 01 Jul 2005 00:46:56 +0000</pubDate>
		<dc:creator>Anthony Persaud</dc:creator>
				<category><![CDATA[Nmap Parser]]></category>

		<guid isPermaLink="false">http://nmapparser.wordpress.com/2005/07/01/new-nmap-parser-website-up-and-running/</guid>
		<description><![CDATA[After learning PHP and MySQL and a whole bunch of javascript &#8211; I can finally get out of using blogger (not that there is anything wrong with that), but now I wrote my own self-maintaining website! I can now write articles, post updates and manage the website right from sourceforge.
If you ever want to contribute [...]]]></description>
			<content:encoded><![CDATA[<p>After learning PHP and MySQL and a whole bunch of javascript &#8211; I can finally get out of using blogger (not that there is anything wrong with that), but now I wrote my own self-maintaining website! I can now write articles, post updates and manage the website right from sourceforge.</p>
<p>If you ever want to contribute articles (tutorials or anything) to the webiste, go to the articles section and use the link provided to send me your content. I will post it for you so everyone else enjoy (it should be Nmap-Parser or Nmap related).</p>
<p>Thanks,</p>
<p>Anthony G Persaud</p>
]]></content:encoded>
			<wfw:commentRss>http://anthonypersaud.com/2005/07/new-nmap-parser-website-up-and-running/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Nmap-Parser to check for suspicioius new services</title>
		<link>http://anthonypersaud.com/2004/11/using-nmap-parser-to-check-for-suspicioius-new-services/</link>
		<comments>http://anthonypersaud.com/2004/11/using-nmap-parser-to-check-for-suspicioius-new-services/#comments</comments>
		<pubDate>Sat, 13 Nov 2004 01:08:56 +0000</pubDate>
		<dc:creator>Anthony Persaud</dc:creator>
				<category><![CDATA[Nmap Parser]]></category>

		<guid isPermaLink="false">http://nmapparser.wordpress.com/2004/11/13/using-nmap-parser-to-check-for-suspicioius-new-services/</guid>
		<description><![CDATA[ ((no less 'of'; my $self)  Using multiple instances of Nmap::Parser is extremely useful in helping audit/monitor the network Policy (ohh noo! its that &#8216;P&#8217; word!). In this example, we have a set of hosts that had been scanned previously for tcp services where the image was saved in base_image.xml. We now will scan [...]]]></description>
			<content:encoded><![CDATA[<p class="articlestext"> (<code>(no less 'of'; my $self)</code>  Using multiple instances of Nmap::Parser is extremely useful in helping audit/monitor the network <strong>P</strong>olicy (ohh noo! its that &#8216;P&#8217; word!). In this example, we have a set of hosts that had been scanned previously for tcp services where the image was saved in base_image.xml. We now will scan the same hosts, and compare if any new tcp have been open since then (good way to look for suspicious new services). Easy security <strong>C</strong>ompliance detection. (ooh noo! The &#8216;C&#8217; word too!).</p>
<pre>use Nmap::Parser;
 use vars qw($nmap_exe $nmap_args @ips);
 my $base = new Nmap::Parser;
 my $curr = new Nmap::Parser;

 $base-&gt;parsefile('base_image.xml'); #load previous state
 $curr-&gt;parsescan($nmap_exe, $nmap_args, @ips); #scan current hosts

 for my $ip ($curr-&gt;get_ips )
 {
        #assume that IPs in base == IPs in curr scan
        my $ip_base = $base-&gt;get_host($ip);
        my $ip_curr = $curr-&gt;get_host($ip);
        my %port = ();

        #find ports that are open that were not open before
        #by finding the difference in port lists
        my @diff =  grep { $port{$_} &lt; 2}
                   (map {$port{$_}++; $_}
                   ( $ip_curr-&gt;tcp_open_ports ,
                     $ip_base-&gt;tcp_open_ports ));

        print "$ip has these new ports open: ".join(',',@diff)
                 if(scalar @diff);

        for (@diff){
                   print "$_ seems to be ",
                            $ip_curr-&gt;tcp_service($_)-&gt;name,
                   "\n";
}

 }</pre>
]]></content:encoded>
			<wfw:commentRss>http://anthonypersaud.com/2004/11/using-nmap-parser-to-check-for-suspicioius-new-services/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
