<?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: Simple Passphrase Conundrum</title>
	<atom:link href="http://www.red-sweater.com/blog/2713/simple-passphrase-conundrum/feed" rel="self" type="application/rss+xml" />
	<link>http://www.red-sweater.com/blog/2713/simple-passphrase-conundrum</link>
	<description>Mac &#38; Technology Writings by Daniel Jalkut</description>
	<lastBuildDate>Thu, 16 May 2013 21:58:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: ChadF</title>
		<link>http://www.red-sweater.com/blog/2713/simple-passphrase-conundrum/comment-page-1#comment-273205</link>
		<dc:creator>ChadF</dc:creator>
		<pubDate>Tue, 07 Aug 2012 05:53:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/?p=2713#comment-273205</guid>
		<description><![CDATA[With so many more sites using SSL by default now for content security, it makes you wonder why client side PKI based authentication hasn&#039;t become more common. Then a place like google (or FB, etc) could still issue certs for users that other sites could &quot;trust&quot;, but aside from the CA cert being cracked/stolen or a user&#039;s private cert key (and passphrase) being directly acquired, it would seem to be a far more secure option. And nothing would stop them (google, etc..) from providing both to each user, a secure cert for all using SSL and a username/password for legacy sites.

While somewhat annoying for normal logins, when resting a password a security question should be needed to prevent blind resets if their email account is hijacked. And if none has been set (or maybe even it it has) then add something else is to make it &quot;less anonymous&quot; for the one doing the resting - maybe a text message to a phone number with an unlock code in addition to the email. Since that has a better chance of being traced (for legal actions) it might at least weed out some of the amateurs out of fear of getting caught.]]></description>
		<content:encoded><![CDATA[<p>With so many more sites using SSL by default now for content security, it makes you wonder why client side PKI based authentication hasn&#8217;t become more common. Then a place like google (or FB, etc) could still issue certs for users that other sites could &#8220;trust&#8221;, but aside from the CA cert being cracked/stolen or a user&#8217;s private cert key (and passphrase) being directly acquired, it would seem to be a far more secure option. And nothing would stop them (google, etc..) from providing both to each user, a secure cert for all using SSL and a username/password for legacy sites.</p>
<p>While somewhat annoying for normal logins, when resting a password a security question should be needed to prevent blind resets if their email account is hijacked. And if none has been set (or maybe even it it has) then add something else is to make it &#8220;less anonymous&#8221; for the one doing the resting &#8211; maybe a text message to a phone number with an unlock code in addition to the email. Since that has a better chance of being traced (for legal actions) it might at least weed out some of the amateurs out of fear of getting caught.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William</title>
		<link>http://www.red-sweater.com/blog/2713/simple-passphrase-conundrum/comment-page-1#comment-273162</link>
		<dc:creator>William</dc:creator>
		<pubDate>Mon, 06 Aug 2012 09:59:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/?p=2713#comment-273162</guid>
		<description><![CDATA[Sounds like it wasn&#039;t his password that was hacked after all - read the updates.

I &quot;solved&quot; the problem with iOS App Store security by setting up a separate iTunes account that I only use for App Store purchases.  So I have a shorter password on that, and a complex one on my actual iCloud account.  Hopefully that foils the hacker... or at least slows him down...]]></description>
		<content:encoded><![CDATA[<p>Sounds like it wasn&#8217;t his password that was hacked after all &#8211; read the updates.</p>
<p>I &#8220;solved&#8221; the problem with iOS App Store security by setting up a separate iTunes account that I only use for App Store purchases.  So I have a shorter password on that, and a complex one on my actual iCloud account.  Hopefully that foils the hacker&#8230; or at least slows him down&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Burghardt</title>
		<link>http://www.red-sweater.com/blog/2713/simple-passphrase-conundrum/comment-page-1#comment-273161</link>
		<dc:creator>Aaron Burghardt</dc:creator>
		<pubDate>Mon, 06 Aug 2012 09:53:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/?p=2713#comment-273161</guid>
		<description><![CDATA[@ Erik: It&#039;s not quite that bad: All of the data is encrypted, so pulling the flash  dumping the flash would result in unreadable dump. Decrypting the dump requires a unique device ID that is built into the hardware, so it can&#039;t be practically brute-forced. Second, by-passing the lock screen requires a boot-rom level exploit, and no known exploits exist for the 4S, iPad 2, or iPad 3. Third, on the devices that have boot-rom exploits (iPhone 4, 3GS, iPad 1), brute-forcing the password is slow, so an 8-character alpha-numeric or 10-digit PIN will take years to by-pass.

@ Daniel: You can make the unlock a little more convenient: you already turned off &quot;Simple Password&quot;, so instead of the 4-digit PIN, you get prompted with a text field and a keyboard. If you set your password to a long numeric one instead of an alpha-numeric, when you unlock the device you will have PIN-style keypad instead of the keyboard, which is much more convenient.  You don&#039;t need a complex password, just a long one---see Steve Gibson&#039;s article and podcast on the haystack. A 10-digit password would take roughly 15 years to brute-force.]]></description>
		<content:encoded><![CDATA[<p>@ Erik: It&#8217;s not quite that bad: All of the data is encrypted, so pulling the flash  dumping the flash would result in unreadable dump. Decrypting the dump requires a unique device ID that is built into the hardware, so it can&#8217;t be practically brute-forced. Second, by-passing the lock screen requires a boot-rom level exploit, and no known exploits exist for the 4S, iPad 2, or iPad 3. Third, on the devices that have boot-rom exploits (iPhone 4, 3GS, iPad 1), brute-forcing the password is slow, so an 8-character alpha-numeric or 10-digit PIN will take years to by-pass.</p>
<p>@ Daniel: You can make the unlock a little more convenient: you already turned off &#8220;Simple Password&#8221;, so instead of the 4-digit PIN, you get prompted with a text field and a keyboard. If you set your password to a long numeric one instead of an alpha-numeric, when you unlock the device you will have PIN-style keypad instead of the keyboard, which is much more convenient.  You don&#8217;t need a complex password, just a long one&#8212;see Steve Gibson&#8217;s article and podcast on the haystack. A 10-digit password would take roughly 15 years to brute-force.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik</title>
		<link>http://www.red-sweater.com/blog/2713/simple-passphrase-conundrum/comment-page-1#comment-273106</link>
		<dc:creator>Erik</dc:creator>
		<pubDate>Sun, 05 Aug 2012 15:02:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/?p=2713#comment-273106</guid>
		<description><![CDATA[I use the 4-digit PIN to keep casual snoops or pranksters out of my phone. But after reading &quot;Hacking and Securing iOS Applications&quot;, I&#039;ve come to realize there is no good way to truly secure the device; an identity thief can pretty easily bypass the lock screen with standard jailbreak software. Much of the data is actually unencrypted. The crazy thing is how quickly this can be done without leaving obvious traces; if someone confiscates your phone for five minutes at a border crossing you should assume you&#039;ve just been hacked.]]></description>
		<content:encoded><![CDATA[<p>I use the 4-digit PIN to keep casual snoops or pranksters out of my phone. But after reading &#8220;Hacking and Securing iOS Applications&#8221;, I&#8217;ve come to realize there is no good way to truly secure the device; an identity thief can pretty easily bypass the lock screen with standard jailbreak software. Much of the data is actually unencrypted. The crazy thing is how quickly this can be done without leaving obvious traces; if someone confiscates your phone for five minutes at a border crossing you should assume you&#8217;ve just been hacked.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edward Marczak</title>
		<link>http://www.red-sweater.com/blog/2713/simple-passphrase-conundrum/comment-page-1#comment-273068</link>
		<dc:creator>Edward Marczak</dc:creator>
		<pubDate>Sun, 05 Aug 2012 05:13:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/?p=2713#comment-273068</guid>
		<description><![CDATA[You mention two-factor authentication, and Google has offered that very means as a way of protecting your account. In this specific instance, it would have made the attack on Mat&#039;s Gmail account not possible, even with the known password gathered from some other source (presumably, in this case, iCloud).

If you have a Google account, you can read about enabling two-factor authentication for it here:

http://googleblog.blogspot.com/2011/02/advanced-sign-in-security-for-your.html]]></description>
		<content:encoded><![CDATA[<p>You mention two-factor authentication, and Google has offered that very means as a way of protecting your account. In this specific instance, it would have made the attack on Mat&#8217;s Gmail account not possible, even with the known password gathered from some other source (presumably, in this case, iCloud).</p>
<p>If you have a Google account, you can read about enabling two-factor authentication for it here:</p>
<p><a href="http://googleblog.blogspot.com/2011/02/advanced-sign-in-security-for-your.html" rel="nofollow">http://googleblog.blogspot.com/2011/02/advanced-sign-in-security-for-your.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew</title>
		<link>http://www.red-sweater.com/blog/2713/simple-passphrase-conundrum/comment-page-1#comment-273061</link>
		<dc:creator>Matthew</dc:creator>
		<pubDate>Sun, 05 Aug 2012 03:55:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/?p=2713#comment-273061</guid>
		<description><![CDATA[Some banks will require you to answer a random &quot;security question&quot; if you login from a different computer than usual.  That wouldn&#039;t be a bad idea for iCloud, but with it being a mobile system, it could be annoying and make it hard to use.]]></description>
		<content:encoded><![CDATA[<p>Some banks will require you to answer a random &#8220;security question&#8221; if you login from a different computer than usual.  That wouldn&#8217;t be a bad idea for iCloud, but with it being a mobile system, it could be annoying and make it hard to use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.red-sweater.com/blog/2713/simple-passphrase-conundrum/comment-page-1#comment-273043</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sat, 04 Aug 2012 22:33:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/?p=2713#comment-273043</guid>
		<description><![CDATA[Read your post, and this afternoon got an email from my bank that there was a failed password attempt on my online banking. Might just be a sign to spend time this evening changing passwords all around.]]></description>
		<content:encoded><![CDATA[<p>Read your post, and this afternoon got an email from my bank that there was a failed password attempt on my online banking. Might just be a sign to spend time this evening changing passwords all around.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Ferguson</title>
		<link>http://www.red-sweater.com/blog/2713/simple-passphrase-conundrum/comment-page-1#comment-273021</link>
		<dc:creator>Nathan Ferguson</dc:creator>
		<pubDate>Sat, 04 Aug 2012 17:57:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.red-sweater.com/blog/?p=2713#comment-273021</guid>
		<description><![CDATA[The regular prompts to enter my Apple ID password when buying and updating apps are what keep me from improving my already tedious-to-enter password. All other services I use have far more secure passwords, saved with 1Password.

I wish iOS worked like desktop iTunes (never thought I&#039;d say that), where my password is only requested when attempting to view/edit my account info. For parents, there could be a preference setting to require a pin code for purchases.

This way, the only thing a hacker could do (in the short term, at least) would be to purchase apps and media -- purchases that Apple could refund me and that I could cut off quickly by canceling the credit card attached to my account.

I guess this still wouldn&#039;t solve the &quot;passphrase conundrum&quot;, though.]]></description>
		<content:encoded><![CDATA[<p>The regular prompts to enter my Apple ID password when buying and updating apps are what keep me from improving my already tedious-to-enter password. All other services I use have far more secure passwords, saved with 1Password.</p>
<p>I wish iOS worked like desktop iTunes (never thought I&#8217;d say that), where my password is only requested when attempting to view/edit my account info. For parents, there could be a preference setting to require a pin code for purchases.</p>
<p>This way, the only thing a hacker could do (in the short term, at least) would be to purchase apps and media &#8212; purchases that Apple could refund me and that I could cut off quickly by canceling the credit card attached to my account.</p>
<p>I guess this still wouldn&#8217;t solve the &#8220;passphrase conundrum&#8221;, though.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced

 Served from: www.red-sweater.com @ 2013-06-19 03:11:10 by W3 Total Cache -->