Comments on: Registration Schemes: Asymmetrical Cryptography http://www.seoxys.com/registration-schemes-asymmetrical-cryptography/ Wed, 27 Feb 2013 21:05:44 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: links for 2009-09-21 | manicwave.com http://www.seoxys.com/registration-schemes-asymmetrical-cryptography/comment-page-1/#comment-14892 links for 2009-09-21 | manicwave.com Mon, 21 Sep 2009 12:03:30 +0000 http://www.seoxys.com/?p=86#comment-14892 [...] Registration Schemes: Asymmetrical Cryptography | seoxys.com (tags: cocoa registration cryptography serial-numbering) Share/Save [...] […] Registration Schemes: Asymmetrical Cryptography | seoxys.com (tags: cocoa registration cryptography serial-numbering) Share/Save […]

]]> By: Dharmender Singh http://www.seoxys.com/registration-schemes-asymmetrical-cryptography/comment-page-1/#comment-14031 Dharmender Singh Tue, 25 Aug 2009 11:33:39 +0000 http://www.seoxys.com/?p=86#comment-14031 Thank you so much Kenneth for sharing code, this helps me a lot. -Dharmender Singh Thank you so much Kenneth for sharing code, this helps me a lot.

-Dharmender Singh

]]> By: Ken http://www.seoxys.com/registration-schemes-asymmetrical-cryptography/comment-page-1/#comment-3607 Ken Thu, 15 May 2008 15:39:22 +0000 http://www.seoxys.com/?p=86#comment-3607 Hi Kenneth: I found this very useful. Thanks for sharing! Sorry to hear about your computer; hope it's back soon. -Ken Hi Kenneth:
I found this very useful. Thanks for sharing!
Sorry to hear about your computer; hope it’s back soon. -Ken

]]> By: kenneth http://www.seoxys.com/registration-schemes-asymmetrical-cryptography/comment-page-1/#comment-3369 kenneth Thu, 01 May 2008 12:35:04 +0000 http://www.seoxys.com/?p=86#comment-3369 David, this blog is pretty much on pause at the moment, along with everything else I do except support, right now... Main computer blown up by the morons at Eskom, waiting for it to come back for repairs... David, this blog is pretty much on pause at the moment, along with everything else I do except support, right now… Main computer blown up by the morons at Eskom, waiting for it to come back for repairs…

]]> By: David M http://www.seoxys.com/registration-schemes-asymmetrical-cryptography/comment-page-1/#comment-3368 David M Thu, 01 May 2008 04:08:34 +0000 http://www.seoxys.com/?p=86#comment-3368 You've got me hooked. Where's part three? I'm going to be needing to implement something pretty soon. Thanks You’ve got me hooked. Where’s part three? I’m going to be needing to implement something pretty soon. Thanks

]]> By: kenneth http://www.seoxys.com/registration-schemes-asymmetrical-cryptography/comment-page-1/#comment-3313 kenneth Sun, 06 Apr 2008 14:04:00 +0000 http://www.seoxys.com/?p=86#comment-3313 Devon, thanks, this was indeed a horrible typo... You're right, it is the <b>public</b> key that should be in the application! And indeed, checking the framework against a hash is a very good idea, and every AquaticPrime app should do that. Devon, thanks, this was indeed a horrible typo… You’re right, it is the public key that should be in the application!

And indeed, checking the framework against a hash is a very good idea, and every AquaticPrime app should do that.

]]> By: Devon http://www.seoxys.com/registration-schemes-asymmetrical-cryptography/comment-page-1/#comment-3312 Devon Sun, 06 Apr 2008 13:36:16 +0000 http://www.seoxys.com/?p=86#comment-3312 Just a typo: "You then verify that the signature is valid using the private key in your app." Should be public key not private key embedded in your shipping app. I think you could improve the security of the Aquatic Prime framework by implementing a hash check in your application. Perform a hash of the whole framework with your favourite hash like SHA1 (MD5 is not secure enough). Embed this hash in your application and obfuscate it if you want so patching the binary is harder. When your app launches it checks the hash of the included framework against it's own hash and would not work if someone tried to replace the framework. I'm sure people might still find a way around that but it would be harder than just replacing a framework. Just a typo:
“You then verify that the signature is valid using the private key in your app.” Should be public key not private key embedded in your shipping app.

I think you could improve the security of the Aquatic Prime framework by implementing a hash check in your application. Perform a hash of the whole framework with your favourite hash like SHA1 (MD5 is not secure enough). Embed this hash in your application and obfuscate it if you want so patching the binary is harder. When your app launches it checks the hash of the included framework against it’s own hash and would not work if someone tried to replace the framework.

I’m sure people might still find a way around that but it would be harder than just replacing a framework.

]]>