Article View: comp.os.linux.misc
Article #60Re: binaries (generated from "C" code)
From: Marcus J. Ranum
Date: Wed, 27 Mar 1996 16:16
Date: Wed, 27 Mar 1996 16:16
19 lines
1456 bytes
1456 bytes
Larry Motylinski <larry@pronet.mpro.net> wrote: >What I used to do is read the CMOS and other eproms (looking for a >serial number or something that made it unique) and then encrypt that >code in a program. The program (when run) would verify this >information. It kinda sucks because you will be the one to get a call >if they change their hardware. And if the system is a hospital's database, or something mission critical and life-threatening, and they change their hardware, you'll get a call from their lawyers if it was your stupid copy protect that caused downtime. Think carefully before you do something that will put your customers out of business as a means of protecting your software against them! mjr. -- Chief Scientist, V-ONE Corporation -- "Security for a connected world" work http://www.v-one.com personal http://www.clark.net/pub/mjr/mjr-top.html
Technical Details
Message-ID:
<4jbpkj$eo5@clark.net>Path:
arc1-ca.pugleaf.net!news.clark.net!not-for-mailReferences:
<4j7pge$9ga@xanadu.io.com> <hendersoDovvs3.20G@netcom.com> <4ja11e$e1m@mpro1.mpro.net>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!news.clark.net!not-for-mail From: mjr@clark.net (Marcus J. Ranum) Newsgroups: comp.os.linux.misc,comp.lang.c,comp.unix.admin,comp.security.unix Subject: Re: binaries (generated from "C" code) Date: 27 Mar 1996 11:16:19 -0500 Organization: V-ONE Corporation Message-ID: <4jbpkj$eo5@clark.net> References: <4j7pge$9ga@xanadu.io.com> <hendersoDovvs3.20G@netcom.com> <4ja11e$e1m@mpro1.mpro.net> NNTP-Posting-Host: explorer.clark.net Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit