<?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: Princeton study: Disk encryption not safe</title>
	<atom:link href="http://www.rlslog.net/princeton-study-disk-encryption-not-safe/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rlslog.net/princeton-study-disk-encryption-not-safe/</link>
	<description>Hot info about new scene releases!</description>
	<lastBuildDate>Mon, 23 Nov 2009 06:02:08 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ireshine</title>
		<link>http://www.rlslog.net/princeton-study-disk-encryption-not-safe/comment-page-1/#comment-245933</link>
		<dc:creator>ireshine</dc:creator>
		<pubDate>Sat, 23 Feb 2008 01:21:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.rlslog.net/princeton-study-disk-encryption-not-safe/#comment-245933</guid>
		<description>how did they dump the RAM to the hard disk? 
&quot;whats the name of the program&quot; and how do you dump the memory under windows, if its not log out? (freeware,not winhex by x-ways)

And if criminal does steel your laptop/PC and finds it encrypted or password protect , in most cases they format the hard drive and try to sale it as fast as possible.</description>
		<content:encoded><![CDATA[<p>how did they dump the RAM to the hard disk?<br />
&#8220;whats the name of the program&#8221; and how do you dump the memory under windows, if its not log out? (freeware,not winhex by x-ways)</p>
<p>And if criminal does steel your laptop/PC and finds it encrypted or password protect , in most cases they format the hard drive and try to sale it as fast as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edd Miles</title>
		<link>http://www.rlslog.net/princeton-study-disk-encryption-not-safe/comment-page-1/#comment-245762</link>
		<dc:creator>Edd Miles</dc:creator>
		<pubDate>Fri, 22 Feb 2008 22:25:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.rlslog.net/princeton-study-disk-encryption-not-safe/#comment-245762</guid>
		<description>@7 that article is wrong. Whilst having the ram soldered onto the mobo makes it virtually impossible to use the attack by removing the ram, it has no protection against booting off an external HDD (If the mac air supports that? Don&#039;t know!) and stealing the data from Ram that way. Requires more time, but is no more secure that the solution being mooted on the truecrypt forums (namely gluing your ram in place [using a glue that can be removed of course, but as long as you pick one that requires heat and to remove it you&#039;d be just as secure!])

@29 it will most probably work. This is not a flaw in the way any encryption software works (With the possible exception of bitlocker which is apparently extra vulnerable) but is rather a problem with the way the hardware the system is built on runs.

@31 Damn straight. If you are *that* worried about someone using this attack on you, you should have far superior protection methods than just encryption!</description>
		<content:encoded><![CDATA[<p>@7 that article is wrong. Whilst having the ram soldered onto the mobo makes it virtually impossible to use the attack by removing the ram, it has no protection against booting off an external HDD (If the mac air supports that? Don&#8217;t know!) and stealing the data from Ram that way. Requires more time, but is no more secure that the solution being mooted on the truecrypt forums (namely gluing your ram in place [using a glue that can be removed of course, but as long as you pick one that requires heat and to remove it you'd be just as secure!])</p>
<p>@29 it will most probably work. This is not a flaw in the way any encryption software works (With the possible exception of bitlocker which is apparently extra vulnerable) but is rather a problem with the way the hardware the system is built on runs.</p>
<p>@31 Damn straight. If you are *that* worried about someone using this attack on you, you should have far superior protection methods than just encryption!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: didijeeeke</title>
		<link>http://www.rlslog.net/princeton-study-disk-encryption-not-safe/comment-page-1/#comment-245731</link>
		<dc:creator>didijeeeke</dc:creator>
		<pubDate>Fri, 22 Feb 2008 21:58:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.rlslog.net/princeton-study-disk-encryption-not-safe/#comment-245731</guid>
		<description>Some1 could break into a datacenter and actualy steal infromation using this methode.
Normaly even if you manage to break in into a datacenter and steal a hard disk. You still have nothing. But using this methode you are able to get the key without any problem. Normaly a secure server is completly locked out even when you have direct acces. Bios is locked out and hard disks are encrypted. On a very secure server this would be a easy way to get the information.</description>
		<content:encoded><![CDATA[<p>Some1 could break into a datacenter and actualy steal infromation using this methode.<br />
Normaly even if you manage to break in into a datacenter and steal a hard disk. You still have nothing. But using this methode you are able to get the key without any problem. Normaly a secure server is completly locked out even when you have direct acces. Bios is locked out and hard disks are encrypted. On a very secure server this would be a easy way to get the information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hikaricore</title>
		<link>http://www.rlslog.net/princeton-study-disk-encryption-not-safe/comment-page-1/#comment-245503</link>
		<dc:creator>hikaricore</dc:creator>
		<pubDate>Fri, 22 Feb 2008 19:54:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.rlslog.net/princeton-study-disk-encryption-not-safe/#comment-245503</guid>
		<description>no sh*t sherlock</description>
		<content:encoded><![CDATA[<p>no sh*t sherlock</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Atlas</title>
		<link>http://www.rlslog.net/princeton-study-disk-encryption-not-safe/comment-page-1/#comment-245486</link>
		<dc:creator>Atlas</dc:creator>
		<pubDate>Fri, 22 Feb 2008 19:35:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.rlslog.net/princeton-study-disk-encryption-not-safe/#comment-245486</guid>
		<description>someone who has sensitive data should not be walking down the street with a laptop turned on. This person needs to find a secure location to access from and never leave the laptop even for a minute. Similarly, you could find out their passwords with keyloggers (unless they are using keyfiles) but then what kind of person savvy enough to set up encryption would not know how to run an AV and firewall and not d/l pr0n exe&#039;s?

This is a wake up call not to be too overconfident in encryption systems. Amen to that. I keep my truecrypt partition on a usb key and find that the fact that it is not always attached makes it more secure.
cheers</description>
		<content:encoded><![CDATA[<p>someone who has sensitive data should not be walking down the street with a laptop turned on. This person needs to find a secure location to access from and never leave the laptop even for a minute. Similarly, you could find out their passwords with keyloggers (unless they are using keyfiles) but then what kind of person savvy enough to set up encryption would not know how to run an AV and firewall and not d/l pr0n exe&#8217;s?</p>
<p>This is a wake up call not to be too overconfident in encryption systems. Amen to that. I keep my truecrypt partition on a usb key and find that the fact that it is not always attached makes it more secure.<br />
cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SupeS</title>
		<link>http://www.rlslog.net/princeton-study-disk-encryption-not-safe/comment-page-1/#comment-245409</link>
		<dc:creator>SupeS</dc:creator>
		<pubDate>Fri, 22 Feb 2008 17:55:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.rlslog.net/princeton-study-disk-encryption-not-safe/#comment-245409</guid>
		<description>NO Harddisk anymore Flashmemory is the future</description>
		<content:encoded><![CDATA[<p>NO Harddisk anymore Flashmemory is the future</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: (O)fer</title>
		<link>http://www.rlslog.net/princeton-study-disk-encryption-not-safe/comment-page-1/#comment-245364</link>
		<dc:creator>(O)fer</dc:creator>
		<pubDate>Fri, 22 Feb 2008 16:49:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.rlslog.net/princeton-study-disk-encryption-not-safe/#comment-245364</guid>
		<description>did they tried this on SECUSTAR products??? its the best disk encryption soft... no shts like truecrypt or other</description>
		<content:encoded><![CDATA[<p>did they tried this on SECUSTAR products??? its the best disk encryption soft&#8230; no shts like truecrypt or other</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ruff McGruff</title>
		<link>http://www.rlslog.net/princeton-study-disk-encryption-not-safe/comment-page-1/#comment-245357</link>
		<dc:creator>Ruff McGruff</dc:creator>
		<pubDate>Fri, 22 Feb 2008 16:42:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.rlslog.net/princeton-study-disk-encryption-not-safe/#comment-245357</guid>
		<description>truecrypt FTW, it does wat it says. more than enough security for a lot of people. and if there is information which is THAT THAT important, dont freakin carry it around in ur damn laptop.</description>
		<content:encoded><![CDATA[<p>truecrypt FTW, it does wat it says. more than enough security for a lot of people. and if there is information which is THAT THAT important, dont freakin carry it around in ur damn laptop.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: .:.</title>
		<link>http://www.rlslog.net/princeton-study-disk-encryption-not-safe/comment-page-1/#comment-245337</link>
		<dc:creator>.:.</dc:creator>
		<pubDate>Fri, 22 Feb 2008 16:24:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.rlslog.net/princeton-study-disk-encryption-not-safe/#comment-245337</guid>
		<description>UPDATE: 

If you don’t see any copies of the pattern, possible explanations include (1) you have ECC (error-correcting) RAM, which the BIOS clears at boot; (2) your BIOS clears RAM at boot for another reason (try disabling the memory test or enabling “Quick Boot” mode); (3) your RAM’s retention time is too short to be noticeable at normal temperatures. In any case, your computer might still be vulnerable — an attacker could cool the RAM so that the data takes longer to decay and/or transfer the memory modules to a computer that doesn’t clear RAM at boot and read them there.


link : http://citp.princeton.edu/memory/exp/</description>
		<content:encoded><![CDATA[<p>UPDATE: </p>
<p>If you don’t see any copies of the pattern, possible explanations include (1) you have ECC (error-correcting) RAM, which the BIOS clears at boot; (2) your BIOS clears RAM at boot for another reason (try disabling the memory test or enabling “Quick Boot” mode); (3) your RAM’s retention time is too short to be noticeable at normal temperatures. In any case, your computer might still be vulnerable — an attacker could cool the RAM so that the data takes longer to decay and/or transfer the memory modules to a computer that doesn’t clear RAM at boot and read them there.</p>
<p>link : <a href="http://citp.princeton.edu/memory/exp/" rel="nofollow">http://citp.princeton.edu/memory/exp/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: .:.</title>
		<link>http://www.rlslog.net/princeton-study-disk-encryption-not-safe/comment-page-1/#comment-245332</link>
		<dc:creator>.:.</dc:creator>
		<pubDate>Fri, 22 Feb 2008 16:20:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.rlslog.net/princeton-study-disk-encryption-not-safe/#comment-245332</guid>
		<description>If you watch the Video then READ about it, it explains that, in the case of &quot;truecrypt&quot;, you follow the INSTRUCTIONs and shutdown cleanly then it NOT a feasable attack...

read &quot;SAS&quot; comment then go look at the truecrypt forums.

the answer is 6 ;)</description>
		<content:encoded><![CDATA[<p>If you watch the Video then READ about it, it explains that, in the case of &#8220;truecrypt&#8221;, you follow the INSTRUCTIONs and shutdown cleanly then it NOT a feasable attack&#8230;</p>
<p>read &#8220;SAS&#8221; comment then go look at the truecrypt forums.</p>
<p>the answer is 6 <img src='http://www.rlslog.net/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rohit</title>
		<link>http://www.rlslog.net/princeton-study-disk-encryption-not-safe/comment-page-1/#comment-245330</link>
		<dc:creator>rohit</dc:creator>
		<pubDate>Fri, 22 Feb 2008 16:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.rlslog.net/princeton-study-disk-encryption-not-safe/#comment-245330</guid>
		<description>hjhjfgjfgjhfgjh yhj gjjfj fgj fg j</description>
		<content:encoded><![CDATA[<p>hjhjfgjfgjhfgjh yhj gjjfj fgj fg j</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rohit</title>
		<link>http://www.rlslog.net/princeton-study-disk-encryption-not-safe/comment-page-1/#comment-245328</link>
		<dc:creator>rohit</dc:creator>
		<pubDate>Fri, 22 Feb 2008 16:18:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.rlslog.net/princeton-study-disk-encryption-not-safe/#comment-245328</guid>
		<description>gyjhfg</description>
		<content:encoded><![CDATA[<p>gyjhfg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rohit</title>
		<link>http://www.rlslog.net/princeton-study-disk-encryption-not-safe/comment-page-1/#comment-245320</link>
		<dc:creator>rohit</dc:creator>
		<pubDate>Fri, 22 Feb 2008 16:14:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.rlslog.net/princeton-study-disk-encryption-not-safe/#comment-245320</guid>
		<description>gyfjkgfhmjh</description>
		<content:encoded><![CDATA[<p>gyfjkgfhmjh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rohit</title>
		<link>http://www.rlslog.net/princeton-study-disk-encryption-not-safe/comment-page-1/#comment-245306</link>
		<dc:creator>rohit</dc:creator>
		<pubDate>Fri, 22 Feb 2008 16:06:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.rlslog.net/princeton-study-disk-encryption-not-safe/#comment-245306</guid>
		<description>it&#039;l&#039; be a very nice product</description>
		<content:encoded><![CDATA[<p>it&#8217;l&#8217; be a very nice product</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nils</title>
		<link>http://www.rlslog.net/princeton-study-disk-encryption-not-safe/comment-page-1/#comment-245247</link>
		<dc:creator>Nils</dc:creator>
		<pubDate>Fri, 22 Feb 2008 15:32:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.rlslog.net/princeton-study-disk-encryption-not-safe/#comment-245247</guid>
		<description>A2DAK, the key for the encryption has to be stored anywhere, or no encryption can happen. And if it is stored, it can be read. To be safe, always turn the device of.</description>
		<content:encoded><![CDATA[<p>A2DAK, the key for the encryption has to be stored anywhere, or no encryption can happen. And if it is stored, it can be read. To be safe, always turn the device of.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
