 




<?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>I.T. Security and Linux Administration &#187; Parsing</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/security-admin/tag/parsing/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/security-admin</link>
	<description>When the penguins and windows can live together, there shall be one.</description>
	<lastBuildDate>Wed, 01 May 2013 03:23:38 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Lighttpd Access Log Parsing</title>
		<link>http://itknowledgeexchange.techtarget.com/security-admin/lighttpd-access-log-parsing/</link>
		<comments>http://itknowledgeexchange.techtarget.com/security-admin/lighttpd-access-log-parsing/#comments</comments>
		<pubDate>Wed, 28 Sep 2011 02:36:15 +0000</pubDate>
		<dc:creator>Eric Hansen</dc:creator>
				<category><![CDATA[Access Log]]></category>
		<category><![CDATA[Bash]]></category>
		<category><![CDATA[Lighttpd]]></category>
		<category><![CDATA[Parsing]]></category>
		<category><![CDATA[scripting]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/security-admin/lighttpd-access-log-parsing/</guid>
		<description><![CDATA[If you&#8217;re like me, you&#8217;re always wanting to parse those pesky log files to make analyzing them easier.  Thankfully, with my constant desire to make my jobs easier (read: make me lazier), and passion for programming, I&#8217;ve written up a quick Bash script to do just this. Now, I&#8217;ll say this right off the bat&#8230;this [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/security-admin/lighttpd-access-log-parsing/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Parsing E-mails via Postfix and PHP</title>
		<link>http://itknowledgeexchange.techtarget.com/security-admin/parsing-e-mails-via-postfix-and-php/</link>
		<comments>http://itknowledgeexchange.techtarget.com/security-admin/parsing-e-mails-via-postfix-and-php/#comments</comments>
		<pubDate>Fri, 09 Sep 2011 17:00:39 +0000</pubDate>
		<dc:creator>Eric Hansen</dc:creator>
				<category><![CDATA[E-mail]]></category>
		<category><![CDATA[Parsing]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Postfix]]></category>
		<category><![CDATA[Virtual]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/security-admin/?p=278</guid>
		<description><![CDATA[While not everyone is going to have a need for this, there are a lot of good reasons to parse e-mail.  Perhaps the best is if you use a help desk/bug tracking/ticket system (Bugtraq, Clientexec, etc&#8230;), and want to allow people to send in requests and such via e-mail.  Among other things, this is the [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/security-admin/parsing-e-mails-via-postfix-and-php/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
