<?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 for Labix Blog</title>
	<atom:link href="http://blog.labix.org/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.labix.org</link>
	<description>by Gustavo Niemeyer</description>
	<lastBuildDate>Wed, 10 Mar 2010 15:15:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Recovering a bootable EBS image by Victor</title>
		<link>http://blog.labix.org/2010/03/09/recovering-a-bootable-ebs-image/comment-page-1#comment-76073</link>
		<dc:creator>Victor</dc:creator>
		<pubDate>Wed, 10 Mar 2010 15:15:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=250#comment-76073</guid>
		<description>Wow. That is so elegant and logical and clearly explained. Brilliantly goes through what could be a complex process and makes it obvious.</description>
		<content:encoded><![CDATA[<p>Wow. That is so elegant and logical and clearly explained. Brilliantly goes through what could be a complex process and makes it obvious.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Breaking into an Android password manager &#8211; Practice by Rik Hemsley</title>
		<link>http://blog.labix.org/2009/12/05/breaking-into-an-android-password-manager-practice/comment-page-1#comment-75412</link>
		<dc:creator>Rik Hemsley</dc:creator>
		<pubDate>Mon, 22 Feb 2010 15:00:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=230#comment-75412</guid>
		<description>I&#039;d like to see your analysis of keepassdroid.</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to see your analysis of keepassdroid.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Breaking into an Android password manager &#8211; Practice by gbrors</title>
		<link>http://blog.labix.org/2009/12/05/breaking-into-an-android-password-manager-practice/comment-page-1#comment-72554</link>
		<dc:creator>gbrors</dc:creator>
		<pubDate>Mon, 07 Dec 2009 19:52:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=230#comment-72554</guid>
		<description>By the way I own and have read parts of the books &quot;Practical cryptography&quot; and &quot;Applied Cryptography&quot; by Bruce Schneier. Even with open source solutions you are forced to enter a long and cryptic master key if you want to defeat brute force attacks.I guess that 99.5% of the users would not do it, but use a weak master key that can be broken with brute force attacks. My solution with the &quot;unlock key&quot; was wrong, but right now I see no real solution to the problem, because the Java cryptography API implemented in the Android system helps brute force attacks by throwing an exception when trying to decode with a wrong master key. If it did not, but just gave back some randomly decoded bytes, I could develop a much more clever solution similar to one that was developed by a German research institute: http://www.mobilesitter.de/en/result.htm</description>
		<content:encoded><![CDATA[<p>By the way I own and have read parts of the books &#8220;Practical cryptography&#8221; and &#8220;Applied Cryptography&#8221; by Bruce Schneier. Even with open source solutions you are forced to enter a long and cryptic master key if you want to defeat brute force attacks.I guess that 99.5% of the users would not do it, but use a weak master key that can be broken with brute force attacks. My solution with the &#8220;unlock key&#8221; was wrong, but right now I see no real solution to the problem, because the Java cryptography API implemented in the Android system helps brute force attacks by throwing an exception when trying to decode with a wrong master key. If it did not, but just gave back some randomly decoded bytes, I could develop a much more clever solution similar to one that was developed by a German research institute: <a href="http://www.mobilesitter.de/en/result.htm" rel="nofollow">http://www.mobilesitter.de/en/result.htm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Breaking into an Android password manager &#8211; Practice by Gustavo Niemeyer</title>
		<link>http://blog.labix.org/2009/12/05/breaking-into-an-android-password-manager-practice/comment-page-1#comment-72524</link>
		<dc:creator>Gustavo Niemeyer</dc:creator>
		<pubDate>Mon, 07 Dec 2009 02:08:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=230#comment-72524</guid>
		<description>Thanks David. Unfortunately, given the comments right above, it looks like he didn&#039;t read it yet.

Gunter, you seem to blame Android for a problem that actually lies in the application itself. No matter how hard it is to disassemble an application (and trust me, other platforms aren&#039;t much harder than this), if the application security depends on not having the source code, the application is badly engineered. Using an obfuscator will just serve to prove that its security is not to be trusted.

Following David&#039;s suggestion and reading some papers and articles by people like Bruce Schneier might be enlightening.</description>
		<content:encoded><![CDATA[<p>Thanks David. Unfortunately, given the comments right above, it looks like he didn&#8217;t read it yet.</p>
<p>Gunter, you seem to blame Android for a problem that actually lies in the application itself. No matter how hard it is to disassemble an application (and trust me, other platforms aren&#8217;t much harder than this), if the application security depends on not having the source code, the application is badly engineered. Using an obfuscator will just serve to prove that its security is not to be trusted.</p>
<p>Following David&#8217;s suggestion and reading some papers and articles by people like Bruce Schneier might be enlightening.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Breaking into an Android password manager &#8211; Practice by David Allouche</title>
		<link>http://blog.labix.org/2009/12/05/breaking-into-an-android-password-manager-practice/comment-page-1#comment-72511</link>
		<dc:creator>David Allouche</dc:creator>
		<pubDate>Sun, 06 Dec 2009 14:02:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=230#comment-72511</guid>
		<description>Nice job Gustavo.

I hope the author of this app will read some Bruce Schneier before making bold security claims the next time.</description>
		<content:encoded><![CDATA[<p>Nice job Gustavo.</p>
<p>I hope the author of this app will read some Bruce Schneier before making bold security claims the next time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Breaking into an Android password manager &#8211; Practice by gbrors</title>
		<link>http://blog.labix.org/2009/12/05/breaking-into-an-android-password-manager-practice/comment-page-1#comment-72506</link>
		<dc:creator>gbrors</dc:creator>
		<pubDate>Sun, 06 Dec 2009 12:59:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=230#comment-72506</guid>
		<description>Thank you for your good work. It shows how easy it is to manipulate and change the Java apps of Android, so it is useless trying to implement a copy protection or registration solution. I&#039;m looking for a good obfuscator, as it might make it more difficult for hackers.
I released version 1.2.0 of gbaSafe where the problem with the weak key is solved.</description>
		<content:encoded><![CDATA[<p>Thank you for your good work. It shows how easy it is to manipulate and change the Java apps of Android, so it is useless trying to implement a copy protection or registration solution. I&#8217;m looking for a good obfuscator, as it might make it more difficult for hackers.<br />
I released version 1.2.0 of gbaSafe where the problem with the weak key is solved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Breaking into an Android password manager &#8211; Theory by Gustavo Niemeyer</title>
		<link>http://blog.labix.org/2009/12/01/breaking-into-an-android-password-manager-theory/comment-page-1#comment-72490</link>
		<dc:creator>Gustavo Niemeyer</dc:creator>
		<pubDate>Sun, 06 Dec 2009 01:01:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=203#comment-72490</guid>
		<description>It&#039;s good to know that some of the issues are being fixed. That said, these comments above just reinforce my worries about the application, unfortunately.

Unbreakable algorithms, dumb thieves, associating the use of good passwords with &quot;absolute&quot; security (it&#039;s &lt;i&gt;some security at all&lt;/i&gt;, really)...

I can&#039;t provide more insight than I already did in these couple of posts at this point, but I do recommend taking a step back and researching a bit more about security before exposing your name next to a security-oriented software which you&#039;re selling people.</description>
		<content:encoded><![CDATA[<p>It&#8217;s good to know that some of the issues are being fixed. That said, these comments above just reinforce my worries about the application, unfortunately.</p>
<p>Unbreakable algorithms, dumb thieves, associating the use of good passwords with &#8220;absolute&#8221; security (it&#8217;s <i>some security at all</i>, really)&#8230;</p>
<p>I can&#8217;t provide more insight than I already did in these couple of posts at this point, but I do recommend taking a step back and researching a bit more about security before exposing your name next to a security-oriented software which you&#8217;re selling people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Breaking into an Android password manager &#8211; Theory by Breaking into an Android password manager &#8211; Practice &#171; Labix Blog</title>
		<link>http://blog.labix.org/2009/12/01/breaking-into-an-android-password-manager-theory/comment-page-1#comment-72487</link>
		<dc:creator>Breaking into an Android password manager &#8211; Practice &#171; Labix Blog</dc:creator>
		<pubDate>Sun, 06 Dec 2009 00:38:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=203#comment-72487</guid>
		<description>[...] Archives            &#171; Breaking into an Android password manager &#8211; Theory [...]</description>
		<content:encoded><![CDATA[<p>[...] Archives            &laquo; Breaking into an Android password manager &#8211; Theory [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Breaking into an Android password manager &#8211; Theory by gbrors</title>
		<link>http://blog.labix.org/2009/12/01/breaking-into-an-android-password-manager-theory/comment-page-1#comment-72483</link>
		<dc:creator>gbrors</dc:creator>
		<pubDate>Sat, 05 Dec 2009 23:13:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=203#comment-72483</guid>
		<description>I&#039;ve changed the program so that by default no key is stored in any way, but the user must enter the long master key when starting the program (the short unlock key is still an option for people like myself that prefer ease of use to absolute security, guessing that normal thieves would not invest much time trying to get my secrets with brute force attacks). So if the user chooses a good master key and doesn&#039;t use the optional unlock key, then the secrets are really unbreakable (with AES-256). The version 1.1.1 will be published on Sunday.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve changed the program so that by default no key is stored in any way, but the user must enter the long master key when starting the program (the short unlock key is still an option for people like myself that prefer ease of use to absolute security, guessing that normal thieves would not invest much time trying to get my secrets with brute force attacks). So if the user chooses a good master key and doesn&#8217;t use the optional unlock key, then the secrets are really unbreakable (with AES-256). The version 1.1.1 will be published on Sunday.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Breaking into an Android password manager &#8211; Theory by ben</title>
		<link>http://blog.labix.org/2009/12/01/breaking-into-an-android-password-manager-theory/comment-page-1#comment-72433</link>
		<dc:creator>ben</dc:creator>
		<pubDate>Fri, 04 Dec 2009 21:47:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labix.org/?p=203#comment-72433</guid>
		<description>I am interested then as to what the best password manager for android would be then? Google Secrets, KeePassDroid, SplashID, etc.?

Thanks for pointing this out either way and hope the Hero is treating you well.</description>
		<content:encoded><![CDATA[<p>I am interested then as to what the best password manager for android would be then? Google Secrets, KeePassDroid, SplashID, etc.?</p>
<p>Thanks for pointing this out either way and hope the Hero is treating you well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
