Re: [Slightly OT] Copy protecting an AU
Re: [Slightly OT] Copy protecting an AU
- Subject: Re: [Slightly OT] Copy protecting an AU
- From: Admiral Quality <email@hidden>
- Date: Sat, 8 May 2010 07:32:18 -0400
I'm not much of a Mac programmer, but my copy protection system from
my Windows VST products worked fine when ported to a Mac VST, (which
I've wrapped with VSTAU to work as an AU.) I use a challenge/response
type CP system, and all I had to change was the source of a machine
unique ID, and instead of using the Windows registry to store the key
data I use a file on the Mac.
My original Windows copy protection code only took a couple of days to
write. Yes, it's been cracked but as you point out, the goal is to
prohibit casual copying as you just can't stop a determined cracker no
matter what you do.
(Unfortunately any details beyond that I can't share on this list, for
obvious reasons.)
- AQ
On Sat, May 8, 2010 at 7:19 AM, tahome izwah <email@hidden> wrote:
> 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
>
_______________________________________________
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