<?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</title>
	<atom:link href="http://anthonypersaud.com/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>I Love San Diego!</title>
		<link>http://anthonypersaud.com/2009/10/i-love-san-diego/</link>
		<comments>http://anthonypersaud.com/2009/10/i-love-san-diego/#comments</comments>
		<pubDate>Mon, 19 Oct 2009 05:50:17 +0000</pubDate>
		<dc:creator>Anthony Persaud</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[san diego]]></category>

		<guid isPermaLink="false">http://anthonypersaud.com/?p=23</guid>
		<description><![CDATA[Julie and I ended up going to Coronado to celebrate a special event by taking a Gondola ride and going out to the Primavera restaurant. Outside the restaurant I took a snapshot of the street and I think it just turned out great!

]]></description>
			<content:encoded><![CDATA[<p>Julie and I ended up going to Coronado to celebrate a special event by taking a Gondola ride and going out to the Primavera restaurant. Outside the restaurant I took a snapshot of the street and I think it just turned out great!<br />
<a href="http://anthonypersaud.com/wp-content/uploads/2009/10/IMG_2812.jpg"><img class="size-medium wp-image-24 alignnone" title="Coronado - San Diego, CA" src="http://anthonypersaud.com/wp-content/uploads/2009/10/IMG_2812-225x300.jpg" alt="Coronado - San Diego, CA" width="225" height="300" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://anthonypersaud.com/2009/10/i-love-san-diego/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<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>Real-Time Scanning &#8211; (no better time() like &#039;now&#039;)</title>
		<link>http://anthonypersaud.com/2005/07/real-time-scanning-no-better-time-like-now/</link>
		<comments>http://anthonypersaud.com/2005/07/real-time-scanning-no-better-time-like-now/#comments</comments>
		<pubDate>Sat, 02 Jul 2005 01:10:57 +0000</pubDate>
		<dc:creator>Anthony Persaud</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://nmapparser.wordpress.com/2005/07/02/real-time-scanning-no-better-time-like-now/</guid>
		<description><![CDATA[ You can run a nmap scan and have the parser parse the information automagically. The only constraint is that you cannot use &#8216;-oX&#8217;, &#8216;-oN&#8217;, or &#8216;-oG&#8217; as one of your arguments for nmap command line parameters passed to parsescan().
 use Nmap::Parser;

 my $np = new Nmap::Parser;
 my @hosts = @ARGV; #get hosts from cmd [...]]]></description>
			<content:encoded><![CDATA[<p class="articlestext"> You can run a nmap scan and have the parser parse the information automagically. The only constraint is that you cannot use &#8216;-oX&#8217;, &#8216;-oN&#8217;, or &#8216;-oG&#8217; as one of your arguments for nmap command line parameters passed to parsescan().</p>
<pre> use Nmap::Parser;

 my $np = new Nmap::Parser;
 my @hosts = @ARGV; #get hosts from cmd line

 #runs the nmap command with hosts and parses it automagically
 $np-&gt;parsescan('/usr/bin/nmap','-sS O -p 1-1023',@hosts);

 for my $host ($np-&gt;all_hosts()){
        print $host-&gt;hostname."\n";
        #do mor stuff...
 }</pre>
]]></content:encoded>
			<wfw:commentRss>http://anthonypersaud.com/2005/07/real-time-scanning-no-better-time-like-now/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
