home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.msdos.programmer
- Path: sparky!uunet!cs.utexas.edu!sun-barr!ames!purdue!yuma!millerje
- From: millerje@CS.ColoState.EDU (Jeff Miller)
- Subject: Re: Copy Protection Information
- Sender: news@yuma.ACNS.ColoState.EDU (News Account)
- Message-ID: <Dec16.161828.77101@yuma.ACNS.ColoState.EDU>
- Date: Wed, 16 Dec 1992 16:18:28 GMT
- References: <18580@mindlink.bc.ca>
- Nntp-Posting-Host: mozart.cs.colostate.edu
- Organization: Colorado State University, Computer Science Department
- Lines: 24
-
- 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.
-
-
- --
- _____________________________________________________________________________
- | |
- | "Nuke the unborn gay whales!" | millerje@cs.colostate.edu | Jeff Miller |
- |_____________________________________________________________________________|
-