Re: Using the serial # in ROM as a copy protection mechanism...?

Article View: comp.sys.next.programmer

Article #2140

Back to comp.sys.next.programmer Previous Next

#2140

From: Edgar Matias
Date: Fri, 18 Dec 1992 21:35

23 lines
1289 bytes

> louie@sayshell.umd.edu (Louis A. Mamakos) writes:
>
> You either trust your users or not. The approach that I like is to
> give the user some piece of information that needs to be supplied to
> enable the application. This piece of information uniquely identified
> the *owner* of the software. That way, if it gets "loose", you know
> who to trace it back to, and thus who violated the terms of the
> software license agreement. This is the approach that I like, and the
> one that I use for the software that I write.

Well, I know for a fact that at least one of my customers has 
violated the trust.  However, I like your scheme.  Question is:
What do you do if/when you find a pirated copy?  Has it happend you
you yet?

Edgar
-- 
Edgar Matias
Input Research Group
University of Toronto
--
I speak for no one...

Technical Details

Message-ID: <1992Dec18.163540.21795@jarvis.csri.toronto.edu>

Path: arc1-ca.pugleaf.net!sparky!uunet!utcsri!dgp.toronto.edu!ematias

References: <1992Dec17.230932.16643@jarvis.csri.toronto.edu> <1gte4tINNs3r@ni.umd.edu>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!utcsri!dgp.toronto.edu!ematias
Newsgroups: comp.sys.next.programmer
From: ematias@dgp.toronto.edu (Edgar Matias)
Subject: Re: Using the serial # in ROM as a copy protection mechanism...?
Message-ID: <1992Dec18.163540.21795@jarvis.csri.toronto.edu>
Organization: CSRI, University of Toronto
References: <1992Dec17.230932.16643@jarvis.csri.toronto.edu> <1gte4tINNs3r@ni.umd.edu>
Date: 18 Dec 92 21:35:41 GMT
Lines: 23

Reply to Parent Message