Path: utzoo!attcan!uunet!sco!jamesm
From: jamesm@sco.COM (James M. Moore)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Suggestion for virus prevention
Keywords: CODE resource virus detection
Message-ID: <1298@viscous.sco.COM>
Date: 16 Jan 89 21:11:43 GMT
References: <1272@viscous.sco.COM> <3614@tekig4.TEK.COM> <27491@ucbvax.BERKELEY.EDU> <10330@well.UUCP>
Reply-To: jamesm@sco.COM (James M. Moore)
Organization: The Santa Cruz Operation, Inc.
Lines: 18

In article <10330@well.UUCP> odawa@well.UUCP (Michael Odawa) writes:
>We also recommend that your program refuse to continue running (i.e., that
>you ExitToShell() after notifying the user) if its integrity has been 
>compromised.

It would probably be better to give the user the choice.  Some people
like to modify code on their own, and this would remove that
possibility.  A dialog box that says something like "The code of this
program has been modified in some way.  If you didn't do it, or you
aren't sure what this means, you've got a problem and should reload
your software.  If you know what you're doing, feel free to press the
OK button..."

-- 
** James Moore **
** Internet:  jamesm@sco.com **
** uucp:  {decvax!microsoft | uunet | ucbvax!ucscc | amd}!sco!jamesm **
** Nil clu no suim ar bith ag SCO ceard a bhfuil me ag scriobh anois. **