tag:blogger.com,1999:blog-6532011216065208777.post381525509572636894..comments2024-01-24T01:40:35.868-08:00Comments on Weapons of Mass Analysis: Solving Binary 300 From the Defcon 2011 Quals Using AndBugswdunlophttp://www.blogger.com/profile/09410793088283629174noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-6532011216065208777.post-21795191469049220962014-04-10T06:29:51.010-07:002014-04-10T06:29:51.010-07:00Have you solved this question? If you have solved,...Have you solved this question? If you have solved, would you tell me ? Thanks!Anonymoushttps://www.blogger.com/profile/15292134716088058943noreply@blogger.comtag:blogger.com,1999:blog-6532011216065208777.post-53022078893856917822011-06-14T21:49:10.800-07:002011-06-14T21:49:10.800-07:00Woo hoo - my app was used as an example at Defcon ...Woo hoo - my app was used as an example at Defcon :-) And I didn't even get a T-shirt...<br /><br />A couple of quick notes:<br /><br />Before the crypto-weenies complain about the simple encryption, I *know* it's weak. It's strong enough for this particular niche, and the documentation repeatedly *says* that it's only for casual use. The real reason is that I can't export strong crypto from the U.S. without an expensive export license. So the code isn't hardened against reverse-engineering simply because that would be a waste of time. Any attack is going to focus on the encrypted files, not the code. And since it's a *free* app, it's not worth the time.<br /><br />My *paid* version uses AES-CBC with a random IV, which, if the NSA hasn't been lying to us these past years, isn't vulnerable to this known-plaintext attack. Even if you have the source code, that wouldn't help decrypt an unknown file. So it's not especially hardened either, although I may add some tamper-detection in the future.Markhttps://www.blogger.com/profile/07174677926225286446noreply@blogger.comtag:blogger.com,1999:blog-6532011216065208777.post-10621793245300504822011-06-14T02:20:25.634-07:002011-06-14T02:20:25.634-07:00Nice! One question, I've been unable to test A...Nice! One question, I've been unable to test AndBug on a real device... if I try to execute any of the commands I always get: <br />File "/usr/local/lib/python2.6/dist-packages/andbug/proto.py", line 67, in read<br /> pkt = conn.recv(req)<br />error: [Errno 104] Connection reset by peer<br /><br />Is there any step by step guide where I can check that everything is setup properly?dreyercitohttps://www.blogger.com/profile/08138319452719124798noreply@blogger.com