<?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: Cold boot encryption attack video</title>
	<atom:link href="http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/feed/" rel="self" type="application/rss+xml" />
	<link>http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/</link>
	<description>Fresh hacks every day</description>
	<lastBuildDate>Tue, 24 Nov 2009 10:52:02 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Cheng</title>
		<link>http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/comment-page-1/#comment-35188</link>
		<dc:creator>Cheng</dc:creator>
		<pubDate>Sat, 17 May 2008 04:44:56 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/05/13/cold-boot-encryption-attack-video/#comment-35188</guid>
		<description>Interesting video but the comment the reporter lady said after the credits really made my day. it took me by surprise and I almost choked on my coffee :D&lt;br&gt;&lt;br&gt;&lt;br&gt;&quot;If only I could unsee..  what Ive seen with these eyes.....  Two girls one cup was just the start&quot;</description>
		<content:encoded><![CDATA[<p>Interesting video but the comment the reporter lady said after the credits really made my day. it took me by surprise and I almost choked on my coffee :D</p>
<p>&#8220;If only I could unsee..  what Ive seen with these eyes&#8230;..  Two girls one cup was just the start&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Appelbaum</title>
		<link>http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/comment-page-1/#comment-35187</link>
		<dc:creator>Jacob Appelbaum</dc:creator>
		<pubDate>Fri, 16 May 2008 01:02:51 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/05/13/cold-boot-encryption-attack-video/#comment-35187</guid>
		<description>Heya Eliot! Thanks for the link and the nice words. Two minor corrections, one is that my last name is spelled with &#039;el&#039; and not &#039;le&#039;: Appelbaum.&lt;br&gt;&lt;br&gt;The other is that while I sure wish I worked for the EFF, I was simply in the EFF offices. This was unclear because the final cut of the video cut out Seth and Peter, they actually work at the EFF and I do not.&lt;br&gt;&lt;br&gt;Thanks again!</description>
		<content:encoded><![CDATA[<p>Heya Eliot! Thanks for the link and the nice words. Two minor corrections, one is that my last name is spelled with &#8216;el&#8217; and not &#8216;le&#8217;: Appelbaum.</p>
<p>The other is that while I sure wish I worked for the EFF, I was simply in the EFF offices. This was unclear because the final cut of the video cut out Seth and Peter, they actually work at the EFF and I do not.</p>
<p>Thanks again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mojo</title>
		<link>http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/comment-page-1/#comment-35186</link>
		<dc:creator>mojo</dc:creator>
		<pubDate>Wed, 14 May 2008 14:32:51 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/05/13/cold-boot-encryption-attack-video/#comment-35186</guid>
		<description>There are simple ways to defeat this, and although not 100% reliable they are pretty effective.&lt;br&gt;&lt;br&gt;You have to consider what sort of situation this attack is likely to be used in. The attacker would have to get to the machine while it is powered on, but be unable to access it due to software security (passwords etc). So, they reboot the system and try to recover the encryption keys from RAM.&lt;br&gt;&lt;br&gt;Why would you need to freeze the RAM if you could just hit the reset button? Well, the reset button might be disconnected, or the BIOS might be set up to do a full memory check which would overwrite every byte in RAM. The only way to be sure to avoid the BIOS wiping RAM would be to power the machine off, reset the BIOS and power it back on. Note that in laptops, even resetting the BIOS (which is typically very difficult as it involved opening the laptop up) often does not clear the power-on password.&lt;br&gt;&lt;br&gt;So, the attacker wants to freeze the RAM and put it into their own machine for reading. It&#039;s going to be hard to freeze it, transport it to the new machine and install it without data loss, but for arguments sake let&#039;s say it&#039;s possible.&lt;br&gt;&lt;br&gt;Most machines have a case open switch, which could be used to trigger a memory wiping program. Assuming the program was intelligent things like encryption keys could be erased in nanoseconds, and the entire RAM in a few seconds. The attacker would have to power off before opening the case, increasing the time before they can freeze the RAM and thus increasing data loss.&lt;br&gt;&lt;br&gt;Really, this kind of attack, assuming you are reasonably well prepared for it, is not particularly effective. For anyone worried about law enforcement, setting the BIOS to do a full memory test and setting a BIOS password is enough to prevent it in most cases. An improvement would be to make sure your BIOS does a full memory test by default (i.e. after being reset). Some mobos do that, if yours doesn&#039;t a BIOS editor might fix that.</description>
		<content:encoded><![CDATA[<p>There are simple ways to defeat this, and although not 100% reliable they are pretty effective.</p>
<p>You have to consider what sort of situation this attack is likely to be used in. The attacker would have to get to the machine while it is powered on, but be unable to access it due to software security (passwords etc). So, they reboot the system and try to recover the encryption keys from RAM.</p>
<p>Why would you need to freeze the RAM if you could just hit the reset button? Well, the reset button might be disconnected, or the BIOS might be set up to do a full memory check which would overwrite every byte in RAM. The only way to be sure to avoid the BIOS wiping RAM would be to power the machine off, reset the BIOS and power it back on. Note that in laptops, even resetting the BIOS (which is typically very difficult as it involved opening the laptop up) often does not clear the power-on password.</p>
<p>So, the attacker wants to freeze the RAM and put it into their own machine for reading. It&#8217;s going to be hard to freeze it, transport it to the new machine and install it without data loss, but for arguments sake let&#8217;s say it&#8217;s possible.</p>
<p>Most machines have a case open switch, which could be used to trigger a memory wiping program. Assuming the program was intelligent things like encryption keys could be erased in nanoseconds, and the entire RAM in a few seconds. The attacker would have to power off before opening the case, increasing the time before they can freeze the RAM and thus increasing data loss.</p>
<p>Really, this kind of attack, assuming you are reasonably well prepared for it, is not particularly effective. For anyone worried about law enforcement, setting the BIOS to do a full memory test and setting a BIOS password is enough to prevent it in most cases. An improvement would be to make sure your BIOS does a full memory test by default (i.e. after being reset). Some mobos do that, if yours doesn&#8217;t a BIOS editor might fix that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Markie</title>
		<link>http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/comment-page-1/#comment-35185</link>
		<dc:creator>Markie</dc:creator>
		<pubDate>Wed, 14 May 2008 12:52:35 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/05/13/cold-boot-encryption-attack-video/#comment-35185</guid>
		<description>pascal:&lt;br&gt;&lt;br&gt;Removing the &quot;super&quot; ram and replacing it with regular ram would avoid this.  Perhaps if you soldered the memory on...&lt;br&gt;&lt;br&gt;Or if every ram manufacturer goes the route of replacing every ram module with &quot;super&quot; ram, then you can sure bet that someone will find a way to disable the process and still use the attack.</description>
		<content:encoded><![CDATA[<p>pascal:</p>
<p>Removing the &#8220;super&#8221; ram and replacing it with regular ram would avoid this.  Perhaps if you soldered the memory on&#8230;</p>
<p>Or if every ram manufacturer goes the route of replacing every ram module with &#8220;super&#8221; ram, then you can sure bet that someone will find a way to disable the process and still use the attack.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: crust</title>
		<link>http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/comment-page-1/#comment-35184</link>
		<dc:creator>crust</dc:creator>
		<pubDate>Wed, 14 May 2008 09:48:58 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/05/13/cold-boot-encryption-attack-video/#comment-35184</guid>
		<description>Maybe not solved in said laptop, but ATM encryption cards have been potted, wrapped in 40AWG wire, and configured with X-ray sensors in addition to the temperature sensor to get around this problem.   Good RAM can keep charge on the caps for a while even after the refresh goes away.</description>
		<content:encoded><![CDATA[<p>Maybe not solved in said laptop, but ATM encryption cards have been potted, wrapped in 40AWG wire, and configured with X-ray sensors in addition to the temperature sensor to get around this problem.   Good RAM can keep charge on the caps for a while even after the refresh goes away.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: random</title>
		<link>http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/comment-page-1/#comment-35183</link>
		<dc:creator>random</dc:creator>
		<pubDate>Wed, 14 May 2008 07:24:09 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/05/13/cold-boot-encryption-attack-video/#comment-35183</guid>
		<description>I didn&#039;t read the instructions: here&#039;s the link to the ad/article:&lt;br&gt;&lt;a href=&quot;http://rfdesign.com/military_defense_electronics/physical-security-encryption-keys-1207/&quot; rel=&quot;nofollow&quot;&gt;http://rfdesign.com/military_defense_electronics/physical-security-encryption-keys-1207/&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I didn&#8217;t read the instructions: here&#8217;s the link to the ad/article:<br /><a href="http://rfdesign.com/military_defense_electronics/physical-security-encryption-keys-1207/" rel="nofollow">http://rfdesign.com/military_defense_electronics/physical-security-encryption-keys-1207/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: random</title>
		<link>http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/comment-page-1/#comment-35182</link>
		<dc:creator>random</dc:creator>
		<pubDate>Wed, 14 May 2008 07:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/05/13/cold-boot-encryption-attack-video/#comment-35182</guid>
		<description>I dunno about foolproof, but Maxim makes a chip that&#039;s very good at dealing with this problem: check out the DS3600 series, as talked about in this article/advertisement.&lt;br&gt;Internal temp-detection mechanism that registers a change in temperature in 100ns and sets a tamper alarm (that&#039;s much faster than the chip can actually be cooled to stop functioning) and once the alarm is set, it blanks all the crypto keys it has onboard.  It also continually rewrites the crypto keys, xoring them each time, so they don&#039;t build up a charge that can be recovered even after they&#039;ve been wiped, and the chip itself is designed with its interface to the board practically unavailable by putting the data pins inside a perimeter of sense pins in a BGA.&lt;br&gt;Other companies have similar things -- and this is stuff being sold on the open market.  Captive fabs building just for the government probably have more interesting stuff yet.&lt;br&gt;</description>
		<content:encoded><![CDATA[<p>I dunno about foolproof, but Maxim makes a chip that&#8217;s very good at dealing with this problem: check out the DS3600 series, as talked about in this article/advertisement.<br />Internal temp-detection mechanism that registers a change in temperature in 100ns and sets a tamper alarm (that&#8217;s much faster than the chip can actually be cooled to stop functioning) and once the alarm is set, it blanks all the crypto keys it has onboard.  It also continually rewrites the crypto keys, xoring them each time, so they don&#8217;t build up a charge that can be recovered even after they&#8217;ve been wiped, and the chip itself is designed with its interface to the board practically unavailable by putting the data pins inside a perimeter of sense pins in a BGA.<br />Other companies have similar things &#8212; and this is stuff being sold on the open market.  Captive fabs building just for the government probably have more interesting stuff yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wolf</title>
		<link>http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/comment-page-1/#comment-35181</link>
		<dc:creator>Wolf</dc:creator>
		<pubDate>Wed, 14 May 2008 03:56:04 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/05/13/cold-boot-encryption-attack-video/#comment-35181</guid>
		<description>Yeah, you could encrypt the ram, and store the key in the processor cache, implementing custom ram that stores  enough power to delete itself on power loss would also be an option.&lt;br&gt;&lt;br&gt;Or you could just, you know, turn off your computer when your done using it...</description>
		<content:encoded><![CDATA[<p>Yeah, you could encrypt the ram, and store the key in the processor cache, implementing custom ram that stores  enough power to delete itself on power loss would also be an option.</p>
<p>Or you could just, you know, turn off your computer when your done using it&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: predator</title>
		<link>http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/comment-page-1/#comment-35180</link>
		<dc:creator>predator</dc:creator>
		<pubDate>Wed, 14 May 2008 03:40:24 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/05/13/cold-boot-encryption-attack-video/#comment-35180</guid>
		<description>what if a person designed an OS that required use of a USB stick that had the encryption key on it...so that all data on the RAM was encrypted...could everything be considered safe then? and if a person removed the stick which cleared RAM automatically?&lt;br&gt;&lt;br&gt;are you safe then?</description>
		<content:encoded><![CDATA[<p>what if a person designed an OS that required use of a USB stick that had the encryption key on it&#8230;so that all data on the RAM was encrypted&#8230;could everything be considered safe then? and if a person removed the stick which cleared RAM automatically?</p>
<p>are you safe then?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eliot</title>
		<link>http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/comment-page-1/#comment-35179</link>
		<dc:creator>Eliot</dc:creator>
		<pubDate>Wed, 14 May 2008 02:00:15 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/05/13/cold-boot-encryption-attack-video/#comment-35179</guid>
		<description>Yeah, I had the audacity of including a link to our February post in this new post. ;)&lt;br&gt;&lt;br&gt;This video is interesting because it comes after several months of talking about the problem. In the first release they hadn&#039;t perfected the ipod or network dump. Jake also mentions that DDR3 can report chip temperature so future bioses could scram if they thought they were being attacked.</description>
		<content:encoded><![CDATA[<p>Yeah, I had the audacity of including a link to our February post in this new post. ;)</p>
<p>This video is interesting because it comes after several months of talking about the problem. In the first release they hadn&#8217;t perfected the ipod or network dump. Jake also mentions that DDR3 can report chip temperature so future bioses could scram if they thought they were being attacked.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/comment-page-1/#comment-35178</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Wed, 14 May 2008 00:23:38 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/05/13/cold-boot-encryption-attack-video/#comment-35178</guid>
		<description>Yeah, this is old news. I wrote about it, back when it was new fresh news full of life! www.webpulp.org/videos/breaking-disk-encryption-with-ram-dumps/</description>
		<content:encoded><![CDATA[<p>Yeah, this is old news. I wrote about it, back when it was new fresh news full of life! <a href="http://www.webpulp.org/videos/breaking-disk-encryption-with-ram-dumps/" rel="nofollow">http://www.webpulp.org/videos/breaking-disk-encryption-with-ram-dumps/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tim</title>
		<link>http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/comment-page-1/#comment-35177</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Wed, 14 May 2008 00:17:49 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/05/13/cold-boot-encryption-attack-video/#comment-35177</guid>
		<description>deja vu!...this was posted here back in February</description>
		<content:encoded><![CDATA[<p>deja vu!&#8230;this was posted here back in February</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tommy</title>
		<link>http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/comment-page-1/#comment-35176</link>
		<dc:creator>tommy</dc:creator>
		<pubDate>Tue, 13 May 2008 22:41:47 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/05/13/cold-boot-encryption-attack-video/#comment-35176</guid>
		<description>@skyler&lt;br&gt;so you advocate keistering your RAM?</description>
		<content:encoded><![CDATA[<p>@skyler<br />so you advocate keistering your RAM?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pascal</title>
		<link>http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/comment-page-1/#comment-35175</link>
		<dc:creator>pascal</dc:creator>
		<pubDate>Tue, 13 May 2008 22:26:17 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/05/13/cold-boot-encryption-attack-video/#comment-35175</guid>
		<description>I don&#039;t know about RAM init procedures, but couldn&#039;t one build chips that, when powered on, ensure they&#039;re filled with all 0&#039;s? so an attacker might freeze them, and build them into another machine in order to read them out etc, but once the machine powers on, data would be erased... (and if this feature is really *inside* the RAM chips, not just on the same board, there should be no way to get around this, as you can&#039;t yet determine the state of every electron inside the chip^^)&lt;br&gt;&lt;br&gt;or is it possible to freeze the RAM in a way that makes it &quot;read-only&quot;?</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know about RAM init procedures, but couldn&#8217;t one build chips that, when powered on, ensure they&#8217;re filled with all 0&#8217;s? so an attacker might freeze them, and build them into another machine in order to read them out etc, but once the machine powers on, data would be erased&#8230; (and if this feature is really *inside* the RAM chips, not just on the same board, there should be no way to get around this, as you can&#8217;t yet determine the state of every electron inside the chip^^)</p>
<p>or is it possible to freeze the RAM in a way that makes it &#8220;read-only&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Skyler Orlando</title>
		<link>http://hackaday.com/2008/05/13/cold-boot-encryption-attack-video/comment-page-1/#comment-35174</link>
		<dc:creator>Skyler Orlando</dc:creator>
		<pubDate>Tue, 13 May 2008 22:19:01 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/05/13/cold-boot-encryption-attack-video/#comment-35174</guid>
		<description>I have a better solution. Remove all ram from your laptop before&lt;br&gt;shutting it down. *evil grin*&lt;br&gt;&lt;br&gt;And store it in a closed bottle of warm water to help the data fade&lt;br&gt;faster...&lt;br&gt;&lt;br&gt;Disclaimer- Do not try this at home, kids! ;)</description>
		<content:encoded><![CDATA[<p>I have a better solution. Remove all ram from your laptop before<br />shutting it down. *evil grin*</p>
<p>And store it in a closed bottle of warm water to help the data fade<br />faster&#8230;</p>
<p>Disclaimer- Do not try this at home, kids! ;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
