Hi I rolled out my own license scheme so that I don’t have to pay anyone. ;) I find that coding license checking methods with Cocoa and Objective-C is terribly unsafe. Objective-C has the nasty habit of exposing classes and their methods, which you can easily access/find out if you know what you are doing (otool and class-dump for starters). I do all my license checking code in C++ or just plain C, and use redundant checking in different places. Another trick I learned in a conference is to use critical variables as static variables rather than class ivars. However, my needs are probably different than yours, but all I’m saying be careful how you expose your licensing code if you are going to use objective C.
Please read this: http://loadcode.blogspot.pt/2006/02/cracking-software-on-os-x.html and this: http://lifehacker.com/5736101/how-to-crack-just-about-any-mac-app-and-how-to-prevent-it HTH J. Varela _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
