Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site uwmacc.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!gamma!epsilon!zeta!sabre!petrus!bellcore!decvax!decwrl!pyramid!ut-sally!seismo!uwvax!uwmacc!demillo
From: demillo@uwmacc.UUCP (Rob DeMillo)
Newsgroups: net.micro.pc
Subject: Re: Re: Copy Protection - a case study
Message-ID: <1811@uwmacc.UUCP>
Date: Mon, 16-Dec-85 14:32:42 EST
Article-I.D.: uwmacc.1811
Posted: Mon Dec 16 14:32:42 1985
Date-Received: Wed, 18-Dec-85 05:03:19 EST
References: <3624@think.UUCP> <131300002@ima.UUCP>
Organization: UWisconsin-Madison Academic Comp Center
Lines: 38

> >	(c) On EVERY distributed diskette, include (somewhere)
> >	    in the code an encrypted serial number. Keep a
> >	    record of which user has which serial number.
> Great.  So what!  You have a record of where you shipped it.  But you rely
> on the customer to send back the card.  Most of us users DO NOT send back that
> dumb little card.  End of bookkeeping.
> >	(d) If you find a pirated copy of your code, check
> >	    the serial number and trace it back to the
> >	    source! 
> Above note says why it won't work.
> >
> >This scheme has several advantages:
> >	(a) Ease of implementation - only need good
> >	    bookkeeping to keep track of the serial #s.
> And users who will send back the cards.
> -- 
> 
> Mr. Video      seismo!uwvax!nicmad!brown

What are you talking about? What card? 

I am talking about the burden of bookkeeping being on the
the company, not the consumer. You produce the diskettes
on demand, and encode the serial number in the diskette.
The consumer doesn't have to send back anything.


-- 
                           --- Rob DeMillo 
                               Madison Academic Computer Center
                               ...seismo!uwvax!uwmacc!demillo


     "...I suppose you find the concept of a 
         robot with an artificial leg amusing?"

                    -- Marvin, the Paranoid Android