Path: utzoo!utgpu!water!watmath!clyde!rutgers!mcnc!gatech!pyr!ccasttd
From: ccasttd@pyr.gatech.EDU (Thomas M. Dixon Jr.)
Newsgroups: comp.sys.amiga
Subject: Re: virus, ARRRG! (really a virus-eating-virus)
Keywords: Bravo, exactally, just_what_the_Dr_ordered
Message-ID: <4763@pyr.gatech.EDU>
Date: 12 Jan 88 18:53:08 GMT
References: <10081@ufcsv.cis.ufl.EDU> <4361@garfield.UUCP>
Reply-To: ccasttd@pyr.UUCP (Thomas M. Dixon Jr.)
Distribution: na
Organization: Georgia Institute of Technology, Atlanta
Lines: 26

In article <4361@garfield.UUCP> john13@garfield.UUCP (John Russell) writes:
>In article <10081@ufcsv.cis.ufl.EDU> soo@beach.cis.ufl.edu (Chong L Soo) writes:
>>I was wondering, since the SCA virus is harmless (sort of), if we let it
>>hang around, wouldn't that stop any future versions of (perhaps harmful)
>>virus that uses the boot block also?  
>
>... what I think he is suggesting is
>something like what I hope the VCheck 2.0 will do -- hang around in memory
>and restore itself after boots, examine the boot block of all bootable disks
>you insert, warn you of a non-standard one, and ask you if it should re-install
>that disk. Commercial games would be safe, and you wouldn't keep having to
>run install yourself.
>
>John
YES...
If this is not what 2.0 will do, lets get 3.0 out immed with this feature.
We need a program that "hangs out" all the time and randomly checks for
system corruption.  Something that follows certain criterion for check   
intervals but also checks willy-nilly to make it hard to defeat.  This way
you all of a sudden get a system window saying "System Corruption Detected:
DF0: Boot Block Corruption." or the like.  I think this config would be the
superior option.

Thomas M Dixon Jr.
ccasttd @ pyr.gatech.edu