🚀 go-pugleaf

millerje@CS.ColoState.EDU (Jeff Miller) writes:

>In article <18580@mindlink.bc.ca> Marc_North@mindlink.bc.ca (Marc North) writes:
>>Apologies if this is in the FAQ... (and if it's vague, too)
>>
>>Can someone please point me to where I can find information about how to
>>implement a copy protection system into my programs? I've searched high and
>>low, both electronically and in print media and I cannot seem to find any
>>references to even concepts, let alone specific techniques in this matter.
>>
>>My aim is to include some sort of code into my program that would, ideally,
>>render any unauthorized copy of an executable unusable.

>Perhaps this should be in the FAQ...

>The general consensus is that copy protection DOESN'T WORK.  Plain and simple.
>You could put multiple layers of protection and someone somewhere will be
>able to break in.  There are many good alternatives which I will leave as an
>exercise for the reader to figure out.

I totally agree.  In the age of networks, copy protected stuff doesn't work.
Most network administrators will say, what?  Copy Protection on this software?
RETURN IT!!!!  Some workstations don't even have floppies/hard drives.

I work with a image processing piece of software worth a over $20K and it has
protection (this is on a SUN SPARC workstation), I'm so peeved at it that 
the company is going to get some bad press real soon.  This software is very
powerful, but a 40 character codeword to get it to go is a bit crazy.  

Ken

--
Ken Lam                                                     (803)-884-7615 (H)
System Administrator                                        (803)-792-4969 (W)
Senior Systems Consultant                                   (803)-792-5446(FAX)
Netware/UNIX System Programmer/Integrator                    lam@jove.cofc.edu
MultiMedia Works & Video Productions ======= Teaching the world in better ways