• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Private Frameworks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Private Frameworks


  • Subject: Re: Private Frameworks
  • From: "Kyle Sluder" <email@hidden>
  • Date: Mon, 14 Jan 2008 23:32:17 -0500

On Jan 14, 2008 7:23 PM, John Stiles <email@hidden> wrote:
> Typically if someone wants to obscure code, I've found that it's the
> part of the code that is responsible for distinguishing the paying
> users from the demo users. (e.g. shareware registrations, or product
> registration keys, or checking the network to see if other copies of
> the same app are active with the same license key).
>
> In my experience, this portion of your code will in fact be analyzed
> by someone, and it is in your best interest to make it obscure.
>
> For other portions of your app, I tend to agree that no one cares.
> Unless money is involved somehow :)

Obfuscation will never secure your copy protection/licensing code.  It
will only present a fun challenge to anyone who wants to crack it.
This has been proven time and again, to the point where Apple's
licensing protection for iWork '08 is laughably pathetic.  Someone
realized that their time was better spent on the product rather than
its copy protection.  (I really wish game companies would understand
this, it might make running games under Wine a little bit more
pleasurable than a midsummer stroll through hell!)

It is impossible to copy-protect software without an external device,
because eventually the CPU has to read your code.  If you have
legitimate concerns about your intellectual property being used by
someone who copies your framework out of your app's bundle and links
to it, then spend the monetary equivalent of the time you would have
devoted to writing copy protection on a lawyer instead.

But if you're as much of a beginner as you confess, then is it really
that likely someone will want to link with your library at all?

--Kyle Sluder
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Private Frameworks
      • From: Alastair Houghton <email@hidden>
References: 
 >Re: Private Frameworks (From: Philippe Casgrain <email@hidden>)
 >Re: Private Frameworks (From: Stefan <email@hidden>)
 >Re: Private Frameworks (From: "Kyle Sluder" <email@hidden>)
 >Re: Private Frameworks (From: John Stiles <email@hidden>)
 >Re: Private Frameworks (From: "Timothy Reaves" <email@hidden>)
 >Re: Private Frameworks (From: John Stiles <email@hidden>)

  • Prev by Date: re: Core Data performance advice... creating relationships.
  • Next by Date: Re: CALayer/CAAnimation doesn't animate
  • Previous by thread: Re: Private Frameworks
  • Next by thread: Re: Private Frameworks
  • Index(es):
    • Date
    • Thread