• 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: [now OT] Licensing/Implementing in Cocoa/Obj-C - Interest in product?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [now OT] Licensing/Implementing in Cocoa/Obj-C - Interest in product?


  • Subject: Re: [now OT] Licensing/Implementing in Cocoa/Obj-C - Interest in product?
  • From: "M. Uli Kusterer" <email@hidden>
  • Date: Wed, 7 Apr 2004 09:33:45 +0200

At 1:20 Uhr +0200 07.04.2004, Stefan Pantke wrote:
- All stuff is C/ObjC

This is what has me worried. It'll be really easy to just turn the relevant check into a NO-OP. No matter how advanced the actual license checking is, as long as this is an option, crackers won't be hindered much. Moreover, this is Objective C we're talking about. With all the dynamic runtime dispatch stuff it has, and its introspection abilities, I gather it'd be ridiculously easy to locate the actual version-checking code.

So, if I'd do this at all, I'd probably settle for a proprietary solution, not open source (even if it's BSD), because in this case, security through obscurity at least means that the crackers will have to crack applications one-by-one. If there is a standardized library, they'd just have to crack that one library, and from then on every ijit could crack other apps using it.

As long as my hand-grown code is good enough to thwart casual piracy, it really doesn't matter if the passwords are generated using an encryption that isn't state-of-the-art. If they want to crack my app, they'll find a way. IMHO it's not worth the hassle trying to discourage use by people who wouldn't have bought my app anyway, especially since it may be an annoyance to those users who *have* actually paid.

Of course, I'm doing mainly Freeware and contract work right now. Maybe my priorities will change once my income depends on the effectiveness of my licensing scheme, who knows?
--
Cheers,
M. Uli Kusterer
------------------------------------------------------------
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.


  • Follow-Ups:
    • Re: [now OT] Licensing/Implementing in Cocoa/Obj-C - Interest in product?
      • From: Christoffer Lerno <email@hidden>
References: 
 >[little OT] Licensing/Implementing in Cocoa/Obj-C (From: Matt Jaffa <email@hidden>)
 >Re: [little OT] Licensing/Implementing in Cocoa/Obj-C (From: Stefan Pantke <email@hidden>)
 >Re: [little OT] Licensing/Implementing in Cocoa/Obj-C (From: Allan Odgaard <email@hidden>)
 >Re: [little OT] Licensing/Implementing in Cocoa/Obj-C (From: Stefan Pantke <email@hidden>)
 >Re: [now OT] Licensing/Implementing in Cocoa/Obj-C (From: Shawn Erickson <email@hidden>)
 >Re: [now OT] Licensing/Implementing in Cocoa/Obj-C - Interest in product? (From: Stefan Pantke <email@hidden>)

  • Prev by Date: Re: resignFirstResponder called immediately
  • Next by Date: Implementing Licensing in C/ObjC/Cocoa (was: Re: [now OT] Licensing/Implementing in Cocoa/Obj-C - Interest in product?)
  • Previous by thread: Re: [now OT] Licensing/Implementing in Cocoa/Obj-C - Interest in product?
  • Next by thread: Re: [now OT] Licensing/Implementing in Cocoa/Obj-C - Interest in product?
  • Index(es):
    • Date
    • Thread