-
Website
http://toxicsoftware.com/ -
Original page
http://toxicsoftware.com/aquaticprime-aftermath/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
schwa
20 comments · 2 points
-
Alexander Mikhalev
1 comment · 1 points
-
myxibrium
1 comment · 1 points
-
somegeekintn
1 comment · 1 points
-
Stewf
2 comments · 1 points
-
-
Popular Threads
-
ICE Amsterdam 09
4 weeks ago · 1 comment
-
ICE Amsterdam 09
We all look forward to your contribution of a usable, bullet-proof, uncrackable licensing scheme
(with source) for shareware developers to use. After your critical analysis of Aquatic Prime, you
now know of at least one way that it shouldn't be done. Good luck and godspeed.
Public-key encryption systems may be especially vulnerable to replacement of the public key,
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.
I'm quite surprised you are getting such a reaction. While you've taking the time to 'prove it'
and point at a specific product, none of this is new. I suppose this is hush flame as we already know
but if you blog about it people will discover these deep dark secrets that already sit on other public
websites :/
I'm not watching your thread, but I'm sure it is the implementors that have banked on this scheme
that are seeing red as it COULD affect their financials. However I'm sure we all know that if someone
is going to go to the trouble to write a SIMBL/InputManager plugin to runtime circumvent your registration
scheme, they probably won't be ponying up for a license anyway. Most pirates take the use it for free
or don't use it at all mentality.
Otherwise MethodSwizzling is cool and fun :)