<?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"
	>
<channel>
	<title>Comments on: The iPhone 3GS and Forensics: Encryption Changes the Game?</title>
	<atom:link href="http://anthonyvance.com/blog/forensics/iphone_encryption/feed/" rel="self" type="application/rss+xml" />
	<link>http://anthonyvance.com/blog/forensics/iphone_encryption/</link>
	<description>Assistant Professor—Information Systems—Brigham Young University</description>
	<pubDate>Thu, 29 Jul 2010 14:51:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Limitations of Data Protection in iOS 4 &#124; Anthony Vance</title>
		<link>http://anthonyvance.com/blog/forensics/iphone_encryption/#comment-209</link>
		<dc:creator>Limitations of Data Protection in iOS 4 &#124; Anthony Vance</dc:creator>
		<pubDate>Thu, 24 Jun 2010 09:59:04 +0000</pubDate>
		<guid isPermaLink="false">http://anthonyvance.com/blog/?p=580#comment-209</guid>
		<description>[...] it&#8217;s important to note what encryption capability the iPhone already had (which I discussed here. The release of the iPhone 3GS (and later iPod Touch 3rd Generation) brought hardware-based full [...]</description>
		<content:encoded><![CDATA[<p>[...] it&#8217;s important to note what encryption capability the iPhone already had (which I discussed here. The release of the iPhone 3GS (and later iPod Touch 3rd Generation) brought hardware-based full [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://anthonyvance.com/blog/forensics/iphone_encryption/#comment-196</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 31 Dec 2009 18:23:24 +0000</pubDate>
		<guid isPermaLink="false">http://anthonyvance.com/blog/?p=580#comment-196</guid>
		<description>Jonathan Zdziarski in a recent webcast (http://www.oreillynet.com/pub/e/1385) has demonstrated that nothing has changed. The encryption on the iPhone 3GS is designed to enable remote wipe, and it works great for this purpose. If the encryption key is wiped, then the data on the device is securely inaccessible.

However, the encryption is not designed to protect the data from hackers and forensics professionals. The iPhone 3GS essentially decrypts data whenever programs make a request for data.</description>
		<content:encoded><![CDATA[<p>Jonathan Zdziarski in a recent webcast (http://www.oreillynet.com/pub/e/1385) has demonstrated that nothing has changed. The encryption on the iPhone 3GS is designed to enable remote wipe, and it works great for this purpose. If the encryption key is wiped, then the data on the device is securely inaccessible.</p>
<p>However, the encryption is not designed to protect the data from hackers and forensics professionals. The iPhone 3GS essentially decrypts data whenever programs make a request for data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Histrionic</title>
		<link>http://anthonyvance.com/blog/forensics/iphone_encryption/#comment-195</link>
		<dc:creator>Histrionic</dc:creator>
		<pubDate>Sun, 20 Dec 2009 02:45:01 +0000</pubDate>
		<guid isPermaLink="false">http://anthonyvance.com/blog/?p=580#comment-195</guid>
		<description>Has any of this changed with the iPhone OS 3.1 update, by any chance? I haven’t seen any concrete information on that, and don’t specifically see it mentioned in Apple’s release notes.</description>
		<content:encoded><![CDATA[<p>Has any of this changed with the iPhone OS 3.1 update, by any chance? I haven’t seen any concrete information on that, and don’t specifically see it mentioned in Apple’s release notes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ski chalets</title>
		<link>http://anthonyvance.com/blog/forensics/iphone_encryption/#comment-193</link>
		<dc:creator>Ski chalets</dc:creator>
		<pubDate>Fri, 07 Aug 2009 12:09:03 +0000</pubDate>
		<guid isPermaLink="false">http://anthonyvance.com/blog/?p=580#comment-193</guid>
		<description>Great info thanks. It was always a worry if my phone was stolen.</description>
		<content:encoded><![CDATA[<p>Great info thanks. It was always a worry if my phone was stolen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kimmo Kemppaala</title>
		<link>http://anthonyvance.com/blog/forensics/iphone_encryption/#comment-190</link>
		<dc:creator>Kimmo Kemppaala</dc:creator>
		<pubDate>Thu, 23 Jul 2009 20:09:48 +0000</pubDate>
		<guid isPermaLink="false">http://anthonyvance.com/blog/?p=580#comment-190</guid>
		<description>Hi,

I just read something about iPhone's encryption from Wired website and I remembered your post about this topic. Check it out if you have not read it yet. http://www.wired.com/gadgetlab/2009/07/iphone-encryption/</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I just read something about iPhone&#8217;s encryption from Wired website and I remembered your post about this topic. Check it out if you have not read it yet. <a href="http://www.wired.com/gadgetlab/2009/07/iphone-encryption/" rel="nofollow">http://www.wired.com/gadgetlab/2009/07/iphone-encryption/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Apple iPhone OS 3.0 For The Enterprise - Marco Nielsen at myITforum.com</title>
		<link>http://anthonyvance.com/blog/forensics/iphone_encryption/#comment-180</link>
		<dc:creator>Apple iPhone OS 3.0 For The Enterprise - Marco Nielsen at myITforum.com</dc:creator>
		<pubDate>Mon, 22 Jun 2009 04:55:11 +0000</pubDate>
		<guid isPermaLink="false">http://anthonyvance.com/blog/?p=580#comment-180</guid>
		<description>[...] has an excellent recap on current thoughts around this new feature and the previous gaps here: http://anthonyvance.com/blog/forensics/iphone_encryption/ Also some interesting comments from the author of the iPhone Forensics book, Jonathan Zdziarski, at [...]</description>
		<content:encoded><![CDATA[<p>[...] has an excellent recap on current thoughts around this new feature and the previous gaps here: <a href="http://anthonyvance.com/blog/forensics/iphone_encryption/" rel="nofollow">http://anthonyvance.com/blog/forensics/iphone_encryption/</a> Also some interesting comments from the author of the iPhone Forensics book, Jonathan Zdziarski, at [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Zdziarski</title>
		<link>http://anthonyvance.com/blog/forensics/iphone_encryption/#comment-176</link>
		<dc:creator>Jonathan Zdziarski</dc:creator>
		<pubDate>Sun, 14 Jun 2009 02:26:09 +0000</pubDate>
		<guid isPermaLink="false">http://anthonyvance.com/blog/?p=580#comment-176</guid>
		<description>Anthony,

This may not be as big an issue depending on how it works. If Apple knew how to properly implement security, my first book on iPhone Forensics wouldn't have been able to be written. Unfortunately for consumers, Apple IMO has a history of reckless regard for "secure" coding practices.

If the 3GS is TPMish then an app on the phone querying data will get unencrypted output at the end of it's read functions, or be able to query the crypto facility itself to decrypt. Since the forensics process of today institutes a recovery agent in memory, it may be able to masquerade as a legitimate process to use the phone against itself for decryption.

If a PIN is used, it may only be used to enable access to the device, and not to decrypt. In this case, you can bypass it all together. If the PIN is needed to decrypt, it's likely you could disable the kill switch after each try so you could brute force it. 

Encrypted backups can already be defeated by simply moving the keychain so depending on whether the entire FS is encrypted or individual files, this could also be an easy solution. The keychain doesn't exist in the user home directory either making the chance of being able to move it likely.

Finally, as is the case with the keychain right now, the keys might be easy to deduce or extract. Lots of guys do reverse engineering so it's likely the method for this will be published at some point. Hell if the baseband computer can be cracked, so can a simple crypto mechanism.

Unlike a computer, the phone needs access to user data just to boot... So the ability to get to this data may not be as big of a deal. There are a number of potential ways around it. The question is: can one out of the hundreds of iPhone hackers out there be smarter than Apple? So far, the odds aren't in Apple's favor.

One important thing to note is that iPhoneOS 3.0 on an iPhone or iPhone 3G uses _no_ disk encryption, and one can easily perform a forensic recovery of the user data by following the same methods outlined in the book. Encrypted backups, iPhone passcodes, and all of the huge privacy leaks in v3.0 are still there. The question is whether Apple will be able to gloss over them all with effective encryption.

As far as the 3GS, only time will tell if the 'S' stands for 'Security'.</description>
		<content:encoded><![CDATA[<p>Anthony,</p>
<p>This may not be as big an issue depending on how it works. If Apple knew how to properly implement security, my first book on iPhone Forensics wouldn&#8217;t have been able to be written. Unfortunately for consumers, Apple IMO has a history of reckless regard for &#8220;secure&#8221; coding practices.</p>
<p>If the 3GS is TPMish then an app on the phone querying data will get unencrypted output at the end of it&#8217;s read functions, or be able to query the crypto facility itself to decrypt. Since the forensics process of today institutes a recovery agent in memory, it may be able to masquerade as a legitimate process to use the phone against itself for decryption.</p>
<p>If a PIN is used, it may only be used to enable access to the device, and not to decrypt. In this case, you can bypass it all together. If the PIN is needed to decrypt, it&#8217;s likely you could disable the kill switch after each try so you could brute force it. </p>
<p>Encrypted backups can already be defeated by simply moving the keychain so depending on whether the entire FS is encrypted or individual files, this could also be an easy solution. The keychain doesn&#8217;t exist in the user home directory either making the chance of being able to move it likely.</p>
<p>Finally, as is the case with the keychain right now, the keys might be easy to deduce or extract. Lots of guys do reverse engineering so it&#8217;s likely the method for this will be published at some point. Hell if the baseband computer can be cracked, so can a simple crypto mechanism.</p>
<p>Unlike a computer, the phone needs access to user data just to boot&#8230; So the ability to get to this data may not be as big of a deal. There are a number of potential ways around it. The question is: can one out of the hundreds of iPhone hackers out there be smarter than Apple? So far, the odds aren&#8217;t in Apple&#8217;s favor.</p>
<p>One important thing to note is that iPhoneOS 3.0 on an iPhone or iPhone 3G uses _no_ disk encryption, and one can easily perform a forensic recovery of the user data by following the same methods outlined in the book. Encrypted backups, iPhone passcodes, and all of the huge privacy leaks in v3.0 are still there. The question is whether Apple will be able to gloss over them all with effective encryption.</p>
<p>As far as the 3GS, only time will tell if the &#8216;S&#8217; stands for &#8216;Security&#8217;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
