<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Chedder Bay Kernel Exploit</title>
	<atom:link href="http://www.nzlinux.com/2009/07/chedder-bay-kernel-exploit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nzlinux.com/2009/07/chedder-bay-kernel-exploit/</link>
	<description>New Zealand Linux Users Community</description>
	<lastBuildDate>Sat, 03 Jul 2010 22:53:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Liz Quilty</title>
		<link>http://www.nzlinux.com/2009/07/chedder-bay-kernel-exploit/comment-page-1/#comment-16</link>
		<dc:creator>Liz Quilty</dc:creator>
		<pubDate>Fri, 17 Jul 2009 21:46:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.nzlinux.com/?p=250#comment-16</guid>
		<description>Thanks for the clarification :)</description>
		<content:encoded><![CDATA[<p>Thanks for the clarification <img src='http://www.nzlinux.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: spender</title>
		<link>http://www.nzlinux.com/2009/07/chedder-bay-kernel-exploit/comment-page-1/#comment-15</link>
		<dc:creator>spender</dc:creator>
		<pubDate>Fri, 17 Jul 2009 21:20:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.nzlinux.com/?p=250#comment-15</guid>
		<description>pulseaudio is not required to exploit the kernel when SELinux is enabled.  In other words, as mentioned in the exploit, having SELinux enabled has actually opened you up to an entire class of kernel vulnerabilities that the vanilla kernel would have protected you against.

-Brad</description>
		<content:encoded><![CDATA[<p>pulseaudio is not required to exploit the kernel when SELinux is enabled.  In other words, as mentioned in the exploit, having SELinux enabled has actually opened you up to an entire class of kernel vulnerabilities that the vanilla kernel would have protected you against.</p>
<p>-Brad</p>
]]></content:encoded>
	</item>
</channel>
</rss>
