<?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>Linux Advocacy</title>
	<atom:link href="http://www.linux-advocacy.org/feed" rel="self" type="application/rss+xml" />
	<link>http://www.linux-advocacy.org</link>
	<description>Linux advice, tips and tricks.</description>
	<lastBuildDate>Sun, 09 Oct 2011 06:07:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>PHP Memory Usage</title>
		<link>http://www.linux-advocacy.org/scripting/php-memory-usage?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=php-memory-usage</link>
		<comments>http://www.linux-advocacy.org/scripting/php-memory-usage#comments</comments>
		<pubDate>Tue, 21 Dec 2010 17:15:33 +0000</pubDate>
		<dc:creator>Pizon</dc:creator>
				<category><![CDATA[Scripting]]></category>

		<guid isPermaLink="false">http://www.linux-advocacy.org/?p=90</guid>
		<description><![CDATA[PHP memory utilization is always an issue with web applications. As of version 5.2.0 there are two useful functions available to help determine application memory usage. The functions are memory_get_peak_usage() and memory_get_usage().  The documentation is rather sparse but the usage of the functions is simple and straightforward.  The main difference between the functions is when [...]]]></description>
		<wfw:commentRss>http://www.linux-advocacy.org/scripting/php-memory-usage/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why Apache Is Affected By Slowloris</title>
		<link>http://www.linux-advocacy.org/web-servers/why-apache-is-affected-by-slowloris?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=why-apache-is-affected-by-slowloris</link>
		<comments>http://www.linux-advocacy.org/web-servers/why-apache-is-affected-by-slowloris#comments</comments>
		<pubDate>Sun, 07 Nov 2010 11:00:40 +0000</pubDate>
		<dc:creator>Pizon</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Web Servers]]></category>

		<guid isPermaLink="false">http://www.linux-advocacy.org/?p=51</guid>
		<description><![CDATA[It&#8217;s been talked about a lot on mailing lists and forums. Recommendations are often made to use nginx, lighttpd, or varnish in front of your web servers to protect Apache but little is said about why Apache is vulnerable to slowloris. The problem with Apache lies with its architecture. For the purpose of this discussion [...]]]></description>
		<wfw:commentRss>http://www.linux-advocacy.org/web-servers/why-apache-is-affected-by-slowloris/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Patch to fix &#8211;textonly option to yaourt on Arch Linux</title>
		<link>http://www.linux-advocacy.org/scripting/patch-to-fix-textonly-option-to-yaourt-on-arch-linux?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=patch-to-fix-textonly-option-to-yaourt-on-arch-linux</link>
		<comments>http://www.linux-advocacy.org/scripting/patch-to-fix-textonly-option-to-yaourt-on-arch-linux#comments</comments>
		<pubDate>Sun, 07 Jun 2009 08:02:13 +0000</pubDate>
		<dc:creator>Pizon</dc:creator>
				<category><![CDATA[Scripting]]></category>

		<guid isPermaLink="false">http://www.linux-advocacy.org/?p=14</guid>
		<description><![CDATA[If you use the yaourt wrapper for pacman on Arch Linux you may have noticed that the --textonly option no longer works properly. After spending some time on various forums, wikis, bug trackers, and Google I was not able to find a solution to this problem. An inspection of the yaourt scripts reveals a stanza [...]]]></description>
		<wfw:commentRss>http://www.linux-advocacy.org/scripting/patch-to-fix-textonly-option-to-yaourt-on-arch-linux/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Short Mail Names Vulnerability In Plesk 8.6.0</title>
		<link>http://www.linux-advocacy.org/mail-servers/short-mail-names-vulnerability-in-plesk-860?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=short-mail-names-vulnerability-in-plesk-860</link>
		<comments>http://www.linux-advocacy.org/mail-servers/short-mail-names-vulnerability-in-plesk-860#comments</comments>
		<pubDate>Tue, 16 Sep 2008 23:55:55 +0000</pubDate>
		<dc:creator>Pizon</dc:creator>
				<category><![CDATA[Mail Servers]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Web Servers]]></category>

		<guid isPermaLink="false">http://www.linux-advocacy.org/mail-servers/short-mail-names-vulnerability-in-plesk-860</guid>
		<description><![CDATA[While troubleshooting a bizarre spam issue on a newly upgraded server I came across the following: http://securitytracker.com/alerts/2008/Sep/1020801.html The vulnerability can be exploited in one of two ways. The attacker can generate a base64 hash using a bogus username that begins with a valid short name on the server. The other option is to generate a [...]]]></description>
		<wfw:commentRss>http://www.linux-advocacy.org/mail-servers/short-mail-names-vulnerability-in-plesk-860/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Plesk PCI Compliance</title>
		<link>http://www.linux-advocacy.org/web-servers/making-plesk-more-pci-compliant?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=making-plesk-more-pci-compliant</link>
		<comments>http://www.linux-advocacy.org/web-servers/making-plesk-more-pci-compliant#comments</comments>
		<pubDate>Fri, 25 Apr 2008 11:33:32 +0000</pubDate>
		<dc:creator>Pizon</dc:creator>
				<category><![CDATA[Legacy]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Web Servers]]></category>

		<guid isPermaLink="false">http://www.linux-advocacy.org/web-servers/making-plesk-more-pci-compliant</guid>
		<description><![CDATA[PCI Compliance Scans are becoming more and more common as more credit card processors require them. Most of the scans use a tool like Nessus and the scan results often contain many false positives. For example, the scans do not take into account practices such as back porting security fixes. Distributions such as Red Hat [...]]]></description>
		<wfw:commentRss>http://www.linux-advocacy.org/web-servers/making-plesk-more-pci-compliant/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Dell Inspiron 1420N:  No Sound On Fedora 8</title>
		<link>http://www.linux-advocacy.org/redhatfedora/dell-inspiron-1420n-no-sound-on-fedora-8?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=dell-inspiron-1420n-no-sound-on-fedora-8</link>
		<comments>http://www.linux-advocacy.org/redhatfedora/dell-inspiron-1420n-no-sound-on-fedora-8#comments</comments>
		<pubDate>Tue, 15 Apr 2008 16:53:12 +0000</pubDate>
		<dc:creator>Pizon</dc:creator>
				<category><![CDATA[Redhat/Fedora]]></category>

		<guid isPermaLink="false">http://www.linux-advocacy.org/redhatfedora/dell-inspiron-1420n-no-sound-on-fedora-8</guid>
		<description><![CDATA[Recently I decided to install Fedora 8 on my laptop. Originally the laptop came with Ubuntu but the hand holding that distro offers was starting to get in my way and it makes more sense for my job to have a Redhat-based distro on my laptop. The installation was quick and painless but the sound [...]]]></description>
		<wfw:commentRss>http://www.linux-advocacy.org/redhatfedora/dell-inspiron-1420n-no-sound-on-fedora-8/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>BASH Functions To Manipulate selinux Policy</title>
		<link>http://www.linux-advocacy.org/redhatfedora/bash-functions-to-manipulate-selinux-policy?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=bash-functions-to-manipulate-selinux-policy</link>
		<comments>http://www.linux-advocacy.org/redhatfedora/bash-functions-to-manipulate-selinux-policy#comments</comments>
		<pubDate>Thu, 06 Mar 2008 13:23:12 +0000</pubDate>
		<dc:creator>Pizon</dc:creator>
				<category><![CDATA[Redhat/Fedora]]></category>
		<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.linux-advocacy.org/redhatfedora/bash-functions-to-manipulate-selinux-policy</guid>
		<description><![CDATA[selinux is a great tool for keeping your server secure. The problem many people run into is properly configuring security policies to allow their services to run properly. Redhat-derived Linux distributions provide the audit2allow utility for easing the creation of selinux policy. To make it even easier to create selinux policies add the following bash [...]]]></description>
		<wfw:commentRss>http://www.linux-advocacy.org/redhatfedora/bash-functions-to-manipulate-selinux-policy/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

