<?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: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: TPM hardware attacks</title>
	<atom:link href="http://rdist.root.org/2007/07/16/tpm-hardware-attacks/feed/" rel="self" type="application/rss+xml" />
	<link>http://rdist.root.org/2007/07/16/tpm-hardware-attacks/</link>
	<description>Embedded security, crypto, software protection</description>
	<lastBuildDate>Mon, 08 Mar 2010 21:19:29 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nate Lawson</title>
		<link>http://rdist.root.org/2007/07/16/tpm-hardware-attacks/#comment-4398</link>
		<dc:creator>Nate Lawson</dc:creator>
		<pubDate>Sat, 19 Jan 2008 19:51:16 +0000</pubDate>
		<guid isPermaLink="false">http://rdist.root.org/2007/07/16/tpm-hardware-attacks/#comment-4398</guid>
		<description>Henrique, right, that&#039;s the direction they&#039;re going per EagleLake (discussed in &lt;a href=&quot;http://rdist.root.org/2007/07/17/tpm-hardware-attacks-part-2/&quot; rel=&quot;nofollow&quot;&gt;this thread&lt;/a&gt;).

I disagree with your assessment of how hard it is to modify an integrated design, though.  There have been some big advances in hobbyist silicon-level hacking, mostly by &lt;a href=&quot;http://www.flylogic.net/&quot; rel=&quot;nofollow&quot;&gt;these guys&lt;/a&gt;.  Since there is no deployed system for revoking TPM keys, opening just one chip suffices to enable attacks against the class.</description>
		<content:encoded><![CDATA[<p>Henrique, right, that&#8217;s the direction they&#8217;re going per EagleLake (discussed in <a href="http://rdist.root.org/2007/07/17/tpm-hardware-attacks-part-2/" rel="nofollow">this thread</a>).</p>
<p>I disagree with your assessment of how hard it is to modify an integrated design, though.  There have been some big advances in hobbyist silicon-level hacking, mostly by <a href="http://www.flylogic.net/" rel="nofollow">these guys</a>.  Since there is no deployed system for revoking TPM keys, opening just one chip suffices to enable attacks against the class.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrique</title>
		<link>http://rdist.root.org/2007/07/16/tpm-hardware-attacks/#comment-4397</link>
		<dc:creator>Henrique</dc:creator>
		<pubDate>Fri, 18 Jan 2008 01:27:30 +0000</pubDate>
		<guid isPermaLink="false">http://rdist.root.org/2007/07/16/tpm-hardware-attacks/#comment-4397</guid>
		<description>Actually, it just means the TPM has to go inside the South or North bridge.  Or inside the SoC for embedded designs.  These are not yet available, AFAIK, but there is no real reason why they couldn&#039;t be made.  SuperIO chips with the TPM embedded inside are already common (my ThinkPad has one, for example) -- too bad that doesn&#039;t disable the reset attack, since it is non-fatal to the platform to reset the SuperIO.

Once you get the TPM inside the core chipset, getting access to the TPM hardware to mess with it without blowing it up all to hell becomes a lot more difficult...</description>
		<content:encoded><![CDATA[<p>Actually, it just means the TPM has to go inside the South or North bridge.  Or inside the SoC for embedded designs.  These are not yet available, AFAIK, but there is no real reason why they couldn&#8217;t be made.  SuperIO chips with the TPM embedded inside are already common (my ThinkPad has one, for example) &#8212; too bad that doesn&#8217;t disable the reset attack, since it is non-fatal to the platform to reset the SuperIO.</p>
<p>Once you get the TPM inside the core chipset, getting access to the TPM hardware to mess with it without blowing it up all to hell becomes a lot more difficult&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate Lawson</title>
		<link>http://rdist.root.org/2007/07/16/tpm-hardware-attacks/#comment-2351</link>
		<dc:creator>Nate Lawson</dc:creator>
		<pubDate>Wed, 18 Jul 2007 20:58:41 +0000</pubDate>
		<guid isPermaLink="false">http://rdist.root.org/2007/07/16/tpm-hardware-attacks/#comment-2351</guid>
		<description>Dries, does it actually say &quot;should&quot;?  Because everyone knows when it comes to security, &quot;should&quot; means no one implements it.  However, with functionality/features, &quot;should&quot; means the same as &quot;mandatory&quot;.  :-)

In any case, it would require a pretty big change in chipsets to cause a LPC reset to reset the whole platform.  At the moment, LPC reset is an output pin on all chipsets I know of, since the southbridge is mainly the one that drives this pin.  If this was changed, then the attack would simply become cutting the trace before grounding the LPC reset pin, not a huge increase in difficulty.</description>
		<content:encoded><![CDATA[<p>Dries, does it actually say &#8220;should&#8221;?  Because everyone knows when it comes to security, &#8220;should&#8221; means no one implements it.  However, with functionality/features, &#8220;should&#8221; means the same as &#8220;mandatory&#8221;.  :-)</p>
<p>In any case, it would require a pretty big change in chipsets to cause a LPC reset to reset the whole platform.  At the moment, LPC reset is an output pin on all chipsets I know of, since the southbridge is mainly the one that drives this pin.  If this was changed, then the attack would simply become cutting the trace before grounding the LPC reset pin, not a huge increase in difficulty.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dries Schellekens</title>
		<link>http://rdist.root.org/2007/07/16/tpm-hardware-attacks/#comment-2344</link>
		<dc:creator>Dries Schellekens</dc:creator>
		<pubDate>Wed, 18 Jul 2007 08:48:29 +0000</pubDate>
		<guid isPermaLink="false">http://rdist.root.org/2007/07/16/tpm-hardware-attacks/#comment-2344</guid>
		<description>The TPM reset has been known from the start by TCG. That is why the TCG specification says something like &quot;resetting a TPM should reset the complete platform&quot;.</description>
		<content:encoded><![CDATA[<p>The TPM reset has been known from the start by TCG. That is why the TCG specification says something like &#8220;resetting a TPM should reset the complete platform&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
