<?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: Hacker or hooker?</title>
	<atom:link href="http://rdist.root.org/2008/07/21/hacker-or-hooker/feed/" rel="self" type="application/rss+xml" />
	<link>http://rdist.root.org/2008/07/21/hacker-or-hooker/</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: wunderbarb</title>
		<link>http://rdist.root.org/2008/07/21/hacker-or-hooker/#comment-4737</link>
		<dc:creator>wunderbarb</dc:creator>
		<pubDate>Wed, 06 Aug 2008 16:52:25 +0000</pubDate>
		<guid isPermaLink="false">http://rdist.wordpress.com/?p=151#comment-4737</guid>
		<description>I have another explanation why encryption is not universal.  Data recovery when user has lost his/her passphrase/password.  And he will forget it, believe me.  Then either you provide a trapdoor (and then we are back to initial place from the point of view of hacker) or he will definitively loose his/her data.

&lt;a href=&quot;http://eric-diehl.com/index.php?lang=En&amp;page=lois&quot; rel=&quot;nofollow&quot;&gt;Law 6:  You are the weakest link&lt;/a&gt;.  Handling of passwords are a difficult task.

By the way, nice blog.  You will hear from me often.  #;-)</description>
		<content:encoded><![CDATA[<p>I have another explanation why encryption is not universal.  Data recovery when user has lost his/her passphrase/password.  And he will forget it, believe me.  Then either you provide a trapdoor (and then we are back to initial place from the point of view of hacker) or he will definitively loose his/her data.</p>
<p><a href="http://eric-diehl.com/index.php?lang=En&amp;page=lois" rel="nofollow">Law 6:  You are the weakest link</a>.  Handling of passwords are a difficult task.</p>
<p>By the way, nice blog.  You will hear from me often.  #;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gastroid</title>
		<link>http://rdist.root.org/2008/07/21/hacker-or-hooker/#comment-4701</link>
		<dc:creator>Gastroid</dc:creator>
		<pubDate>Mon, 21 Jul 2008 18:01:30 +0000</pubDate>
		<guid isPermaLink="false">http://rdist.wordpress.com/?p=151#comment-4701</guid>
		<description>I may be talking out of a random orifice, but I would guess encryption is not universal because it hurts performance too much on system with a 300 MHz processor.

How easy is it to patch flash without JTAG?

Company Blackberries do have required passwords and auto-lock screens (mine locked after 1 minute inactivity, or as soon as I put it in holster).  I think the &#039;consumer&#039; variety don&#039;t do that, but I&#039;ve never had one so I&#039;m not sure.</description>
		<content:encoded><![CDATA[<p>I may be talking out of a random orifice, but I would guess encryption is not universal because it hurts performance too much on system with a 300 MHz processor.</p>
<p>How easy is it to patch flash without JTAG?</p>
<p>Company Blackberries do have required passwords and auto-lock screens (mine locked after 1 minute inactivity, or as soon as I put it in holster).  I think the &#8216;consumer&#8217; variety don&#8217;t do that, but I&#8217;ve never had one so I&#8217;m not sure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate Lawson</title>
		<link>http://rdist.root.org/2008/07/21/hacker-or-hooker/#comment-4700</link>
		<dc:creator>Nate Lawson</dc:creator>
		<pubDate>Mon, 21 Jul 2008 16:50:22 +0000</pubDate>
		<guid isPermaLink="false">http://rdist.wordpress.com/?p=151#comment-4700</guid>
		<description>I have a dumb question.  Why isn&#039;t encryption built-in with no option to enable or disable it?  There&#039;s an easy way to add encryption at the factory.

I&#039;m looking at this teardown of the &lt;a href=&quot;http://www.mobilehandsetdesignline.com/howto/baseband_multimedia_processing/showArticle.jhtml?articleID=191801614&quot; rel=&quot;nofollow&quot;&gt;Blackberry 8700&lt;/a&gt;.  It has an Intel PXA (was XScale) processor with NOR flash and SDRAM in the same package.  So, when you install the OS for the first time in the factory, it would create a random encryption key and all data that was written to the external, bulk storage flash could be encrypted with it.  That key would then be encrypted with the default password (&quot;password&quot;?) and written to the internal flash.

When a user took delivery of the device, they could change the password and thus the encrypted key.  As long as no one had dumped the internal NOR flash before the user set a password, the original key would just be decrypted with the default and re-encrypted with the new passphrase.  If the user was paranoid, they could request re-encryption of all the data under a new key instead.

Some day that will be expected of manufacturers.  As for attacking a Blackberry today, it&#039;s likely that the device does not auto-lock and require a password so you can transfer data off it just like the user would.  To catch dumb thieves, it would probably suffice to review Blackberry server logs for outgoing messages.

For hardware attacks, it seems the external flash is NOR as well.  That is not as cheap as NAND so it&#039;s possible they execute directly out of it.  If that&#039;s the case, pick a binary and patch it to get root.</description>
		<content:encoded><![CDATA[<p>I have a dumb question.  Why isn&#8217;t encryption built-in with no option to enable or disable it?  There&#8217;s an easy way to add encryption at the factory.</p>
<p>I&#8217;m looking at this teardown of the <a href="http://www.mobilehandsetdesignline.com/howto/baseband_multimedia_processing/showArticle.jhtml?articleID=191801614" rel="nofollow">Blackberry 8700</a>.  It has an Intel PXA (was XScale) processor with NOR flash and SDRAM in the same package.  So, when you install the OS for the first time in the factory, it would create a random encryption key and all data that was written to the external, bulk storage flash could be encrypted with it.  That key would then be encrypted with the default password (&#8220;password&#8221;?) and written to the internal flash.</p>
<p>When a user took delivery of the device, they could change the password and thus the encrypted key.  As long as no one had dumped the internal NOR flash before the user set a password, the original key would just be decrypted with the default and re-encrypted with the new passphrase.  If the user was paranoid, they could request re-encryption of all the data under a new key instead.</p>
<p>Some day that will be expected of manufacturers.  As for attacking a Blackberry today, it&#8217;s likely that the device does not auto-lock and require a password so you can transfer data off it just like the user would.  To catch dumb thieves, it would probably suffice to review Blackberry server logs for outgoing messages.</p>
<p>For hardware attacks, it seems the external flash is NOR as well.  That is not as cheap as NAND so it&#8217;s possible they execute directly out of it.  If that&#8217;s the case, pick a binary and patch it to get root.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gastroid</title>
		<link>http://rdist.root.org/2008/07/21/hacker-or-hooker/#comment-4699</link>
		<dc:creator>Gastroid</dc:creator>
		<pubDate>Mon, 21 Jul 2008 15:11:18 +0000</pubDate>
		<guid isPermaLink="false">http://rdist.wordpress.com/?p=151#comment-4699</guid>
		<description>Talking about defenses against attackers with possession of the device, you might notice that even if you still someone&#039;s Blackberry, you&#039;re not home free to getting the data off of it.

It wipes the data if you try the wrong password 10 times.  So assuming the user didn&#039;t have its native encryption turned on (articles seem to imply that Mr Downing Street Casanova didn&#039;t), you still have to have 0day to beat the lock, or else you have to open it up to take the flash off the board (anyone know how easy/hard this is?).  I have heard from friends who play with this sort of thing that Blackberries don&#039;t have JTAG exposed.</description>
		<content:encoded><![CDATA[<p>Talking about defenses against attackers with possession of the device, you might notice that even if you still someone&#8217;s Blackberry, you&#8217;re not home free to getting the data off of it.</p>
<p>It wipes the data if you try the wrong password 10 times.  So assuming the user didn&#8217;t have its native encryption turned on (articles seem to imply that Mr Downing Street Casanova didn&#8217;t), you still have to have 0day to beat the lock, or else you have to open it up to take the flash off the board (anyone know how easy/hard this is?).  I have heard from friends who play with this sort of thing that Blackberries don&#8217;t have JTAG exposed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evan S</title>
		<link>http://rdist.root.org/2008/07/21/hacker-or-hooker/#comment-4698</link>
		<dc:creator>Evan S</dc:creator>
		<pubDate>Mon, 21 Jul 2008 15:03:10 +0000</pubDate>
		<guid isPermaLink="false">http://rdist.wordpress.com/?p=151#comment-4698</guid>
		<description>This post reminds me of a quote attributed to Bob Morris (the elder). Paraphrasing: When considering the security of information, don&#039;t forget about the 3 B&#039;s: Blackmail, Bribery, and Burglary. Typically, it is the cheapest of those three that ends up getting the job done.</description>
		<content:encoded><![CDATA[<p>This post reminds me of a quote attributed to Bob Morris (the elder). Paraphrasing: When considering the security of information, don&#8217;t forget about the 3 B&#8217;s: Blackmail, Bribery, and Burglary. Typically, it is the cheapest of those three that ends up getting the job done.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
