This is a fight you cannot win, so don't waste your time. A dedicated cracker will bypass any protection. I use minimal obfuscation and asymmetric key generation, and that's it.
Gleb On 13 January 2015 at 02:32, Graham Cox <graham....@bigpond.com> wrote: > > > On 13 Jan 2015, at 1:18 pm, Charles Srstka <cocoa...@charlessoft.com> > wrote: > > > > Now I just put it in plain C/Obj-C functions, because: > > > > 1. The assembly is always there. > > > I agree about just using plain code, as the obfuscation is in the source > mostly, not the resulting object code. > > But if it's built from macros, and then those macros are used whenever you > need to check against licensed/unlicensed, then at least that forces a > would-be attacker to patch every place, not just one. Chances are the work > involved isn't worth the effort. > > --Graham > > > _______________________________________________ > > 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/glebd70%40gmail.com > > This email sent to gleb...@gmail.com > _______________________________________________ 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
