[Slightly OT] Copy protecting an AU
[Slightly OT] Copy protecting an AU
- Subject: [Slightly OT] Copy protecting an AU
- From: tahome izwah <email@hidden>
- Date: Sat, 8 May 2010 13:19:49 +0200
Hi all,
I am currently looking at improving the copy protection of our Cocoa
based AU plug ins and I'd like to hear what strategy (or maybe
commercial solution) has proven to work best for your products so I
can make an informed decision.
I'm looking for first-hand experience from people who have actually
implemented and shipped a product with their solution as I am very
much aware of the various strategies and the theory behind
implementing copy protection. I also know that there is no
"uncrackable" solution but I'd like to buy ourselves as much time as
possible and would like to minimize casual copying. Any insight
(pointers, tools etc) would be greatly appreciated. We're looking for
a software-only solution.
Also, since our products are Cocoa based stripping symbols doesn't do
much as the Cocoa classes still carry a lot of information in them
that makes it possible for hackers to reverse engineer the code to
remove protection. Are there any tools to obfuscate (or preferably
remove) class information from NSObject subclasses?
Thanks!!
--th
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden