Dwayne Reid wrote:
> However, we are thinking of polishing it up and releasing it for 
> outside use.  What I do NOT want to see is us sell a few copies of 
> this, then not sell any more of them because someone decided to share 
> their copy with the whole world.
> 
> So: I am wondering about a punitive approach to uncontrolled release.
[snip]

What you're talking about is similar to the protection system used on Cadsoft 
EAGLE. You have the application, which checks for a licence key file. That key 
file contains (IIRC):
   Name
   Company name
   Full mailing address
   Licence serial number
   Licence levels (Windows/Linux, Lite/Standard/Pro)

.. So by sharing your copy, you have to give out your keyfile - changing any 
of the data invalidates the licence, so the 'leaked' key points right back to 
the releaser.

The problem you have is, what if someone copied the licence without the 
owner's knowledge or permission - in that case, you have two separate 
licences. One stays on the install disc and needs an install key (say, a 
16-digit alphanumeric string) to activate it. When that licence is activated, 
its data is copied onto the hard disc and 'signed' with a machine-specific 
code (maybe read the C: drive volume label and volume serial number?). Copying 
that won't do you any good - it won't run on any machine other than the one it 
was installed on.

All I'm going to say is, you can generally do what you want, but many 
customers will actively avoid your product if they feel the licensing method 
is too obstructive. Don't use Product Activation or anything that modifies 
hard disc sectors (read: anything like the Macrovision protection systems).

Also consider making your software downgrade into a demo version in the event 
it is copied. That way people can see what it can do, and might actually buy 
it as opposed to using their friends' licences.

Ultimately it's going to be pirated whatever you do - it's basically an arms 
race. All you can really do is slow the pirates down. Even Windows XP Product 
Activation got cracked in the end. Remember that you're only really going to 
stop casual copying - the real pirates are going to copy your software 
whatever you do, so don't spend an excessive amount of time and money trying 
to defend against them, only to find a crack or key-generator on P2P two days 
after release.

In case you can't tell, I've done this sort of thing before... :P

Thanks.
-- 
Phil.                         |  (\_/)  This is Bunny. Copy and paste Bunny
piclist@philpem.me.uk         | (='.'=) into your signature to help him gain
http://www.philpem.me.uk/     | (")_(") world domination.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist