<?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/"
	xmlns:go='http://ns.gigaom.com/'
xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Intel Hyper-Threading A Security Hole</title>
	<atom:link href="http://gigaom.com/2005/05/23/intel-hyper-threading-a-security-hole/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2005/05/23/intel-hyper-threading-a-security-hole/</link>
	<description></description>
	<lastBuildDate>Fri, 10 Feb 2012 20:04:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: idl3mind.net &#187; Blog Archive &#187; Intel Hyper-Threading A Security Hole</title>
		<link>http://gigaom.com/2005/05/23/intel-hyper-threading-a-security-hole/#comment-103480</link>
		<dc:creator><![CDATA[idl3mind.net &#187; Blog Archive &#187; Intel Hyper-Threading A Security Hole]]></dc:creator>
		<pubDate>Tue, 24 May 2005 14:16:08 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2005/05/23/intel-hyper-threading-a-security-hole/#comment-103480</guid>
		<description><![CDATA[[...] ding immediately; single-user systems (i.e., desktop computers) are not affected.â? 	[via Gigaom.com]  	 				 				 					 						This entry was posted 						  						on T [...]]]></description>
		<content:encoded><![CDATA[<p>[...] ding immediately; single-user systems (i.e., desktop computers) are not affected.â? 	[via Gigaom.com]  	 				 				 					 						This entry was posted 						  						on T [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: idl3mind.net &#187; Blog Archive &#187; Intel Hyper-Threading A Security Hole</title>
		<link>http://gigaom.com/2005/05/23/intel-hyper-threading-a-security-hole/#comment-114741</link>
		<dc:creator><![CDATA[idl3mind.net &#187; Blog Archive &#187; Intel Hyper-Threading A Security Hole]]></dc:creator>
		<pubDate>Tue, 24 May 2005 14:16:08 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2005/05/23/intel-hyper-threading-a-security-hole/#comment-114741</guid>
		<description><![CDATA[[...] ding immediately; single-user systems (i.e., desktop computers) are not affected.â? 	[via Gigaom.com]  	 				 				 					 						This entry was posted 						  						on T [...]]]></description>
		<content:encoded><![CDATA[<p>[...] ding immediately; single-user systems (i.e., desktop computers) are not affected.â? 	[via Gigaom.com]  	 				 				 					 						This entry was posted 						  						on T [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: idl3mind.net &#187; Blog Archive &#187; Intel Hyper-Threading A Security Hole</title>
		<link>http://gigaom.com/2005/05/23/intel-hyper-threading-a-security-hole/#comment-168485</link>
		<dc:creator><![CDATA[idl3mind.net &#187; Blog Archive &#187; Intel Hyper-Threading A Security Hole]]></dc:creator>
		<pubDate>Tue, 24 May 2005 14:16:08 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2005/05/23/intel-hyper-threading-a-security-hole/#comment-168485</guid>
		<description><![CDATA[[...] ding immediately; single-user systems (i.e., desktop computers) are not affected.â? 	[via Gigaom.com]  	 				 				 					 						This entry was posted 						  						on T [...]]]></description>
		<content:encoded><![CDATA[<p>[...] ding immediately; single-user systems (i.e., desktop computers) are not affected.â? 	[via Gigaom.com]  	 				 				 					 						This entry was posted 						  						on T [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: O. Hardison</title>
		<link>http://gigaom.com/2005/05/23/intel-hyper-threading-a-security-hole/#comment-103479</link>
		<dc:creator><![CDATA[O. Hardison]]></dc:creator>
		<pubDate>Mon, 23 May 2005 20:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2005/05/23/intel-hyper-threading-a-security-hole/#comment-103479</guid>
		<description><![CDATA[Not to be semantic zealot, but the comment &quot;an attack could expose SSL certificates on shared servers...&quot; is a bit odd considering that certificates are intended to convey the public part of the public/private keys.  Exposing that part of SSL is hardly a concern.  No doubt that the author meant instead that the private key could be exposed in the raw - a critical flaw.]]></description>
		<content:encoded><![CDATA[<p>Not to be semantic zealot, but the comment &#8220;an attack could expose SSL certificates on shared servers&#8230;&#8221; is a bit odd considering that certificates are intended to convey the public part of the public/private keys.  Exposing that part of SSL is hardly a concern.  No doubt that the author meant instead that the private key could be exposed in the raw &#8211; a critical flaw.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gizmodo</title>
		<link>http://gigaom.com/2005/05/23/intel-hyper-threading-a-security-hole/#comment-103478</link>
		<dc:creator><![CDATA[Gizmodo]]></dc:creator>
		<pubDate>Mon, 23 May 2005 16:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2005/05/23/intel-hyper-threading-a-security-hole/#comment-103478</guid>
		<description><![CDATA[&lt;strong&gt;Intel Hyper-Threading Possible Security Hole&lt;/strong&gt;

The title says it all, but don&#039;t throw out your gaming rig quite yet. This security hole affects mostly machines doing multi-user operations (think &#039;webservers&#039; doing secure transactions) and is, according to Linux Torvolds, not &quot;all that worrying ...]]></description>
		<content:encoded><![CDATA[<p><strong>Intel Hyper-Threading Possible Security Hole</strong></p>
<p>The title says it all, but don&#8217;t throw out your gaming rig quite yet. This security hole affects mostly machines doing multi-user operations (think &#8216;webservers&#8217; doing secure transactions) and is, according to Linux Torvolds, not &#8220;all that worrying &#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

