This can be quite a religious argument, but speaking from experience of code 
that's been rigorously hacked time and again, the only effective way to disable 
parts of your code is to not have that code in the executable.  E.G. a compile 
a demo version, and a real licensed version.  Having code execute dependent on 
some switch, regardless of the number or sophistication of the switches, can be 
hacked.  Period.

________________________________
From: Graham Lee <l...@thaesofereode.info>

I disagree. If it's based on a tried and tested (and occasionally formally 
verified) crypto system, knowing the algorithm doesn't lead to a crack. 
Weaknesses would come through bugs in the framework (or incorrect application 
of it), and the more people who can see the source the greater chance there is 
that good people as well as bad can find the issues. Good people fix 'em.
_______________________________________________

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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to