http://toxicsoftware.disqus.com/enFri, 09 Jun 2006 12:54:50 -0000http://toxicsoftware.com/aquaticprime-aftermath/#comment-1655972"Any scheme accessed via Cocoa calls is vulnerable to attack via an InputManager" and<br>Public-key encryption systems may be especially vulnerable to replacement of the public key,<br>unless it is obfuscated throughout the entire app" which are clearly documented in discussion on CocoaDev:MakingSecureRegistrationCodes shouldn't be the first time these guys have heard this.<br><br>I'm quite surprised you are getting such a reaction. While you've taking the time to 'prove it'<br>and point at a specific product, none of this is new. I suppose this is hush flame as we already know<br>but if you blog about it people will discover these deep dark secrets that already sit on other public<br>websites :/<br><br>I'm not watching your thread, but I'm sure it is the implementors that have banked on this scheme<br>that are seeing red as it COULD affect their financials. However I'm sure we all know that if someone<br>is going to go to the trouble to write a SIMBL/InputManager plugin to runtime circumvent your registration<br>scheme, they probably won't be ponying up for a license anyway. Most pirates take the use it for free<br>or don't use it at all mentality.<br><br>Otherwise MethodSwizzling is cool and fun :)Mark GrimesFri, 09 Jun 2006 12:54:50 -0000http://toxicsoftware.com/aquaticprime-aftermath/#comment-1655971Because after pointing out a bug in an existing system it is now obviously my responsible to create a replacement for that system.schwaFri, 09 Jun 2006 09:20:46 -0000http://toxicsoftware.com/aquaticprime-aftermath/#comment-1655970Jonathon,<br><br>We all look forward to your contribution of a usable, bullet-proof, uncrackable licensing scheme <br>(with source) for shareware developers to use. After your critical analysis of Aquatic Prime, you<br>now know of at least one way that it shouldn't be done. Good luck and godspeed.Some GuyFri, 09 Jun 2006 08:02:33 -0000