Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!ptsfa!ihnp4!homxb!mtuxo!mtune!codas!usfvax2!jc3b21!fgd3
From: fgd3@jc3b21.UUCP (Fabbian G. Dufoe)
Newsgroups: comp.sys.amiga
Subject: Re: Virus
Message-ID: <187@jc3b21.UUCP>
Date: Fri, 9-Oct-87 11:39:50 EDT
Article-I.D.: jc3b21.187
Posted: Fri Oct  9 11:39:50 1987
Date-Received: Sun, 11-Oct-87 17:39:58 EDT
References: <650@rocky.STANFORD.EDU>
Organization: St. Petersburg Jr. College, FL
Lines: 28
Summary: That doesn't guarantee safety.

In article <650@rocky.STANFORD.EDU>, rokicki@rocky.STANFORD.EDU (Tomas Rokicki) writes:
> Because I never boot from anyone else's disks, but rather copy
> their software onto one of my customized workbench disks, I am
> quite safe from the virus.  I suspect a number of other people
> work this way too.

     You might be safe from this particular virus, but that technique
certainly won't guarantee safety from any destructive software.  Consider
how simple it would be to have a program open the boot file on your
Workbench disk, install a patch, close the file, and then perform some
routine task that makes it look like a normal, healthy program.  Then, next
time you boot from that Workbench disk you get a "gotcha" message.

     If you don't know what's in the software you are copying to your
customized Workbench disks you are at risk.  One approach is a quarantine:
use software that might be corrupt with Kickstart and Workbench disks that
are never used with any of your good software.  Sterilize your system (by
cold starting) after every use of suspect software before using the good
stuff.  Once you have used a suspect program long enough to feel confident
it isn't infected you can transfer it to your good stuff, but there is
always a slight risk.

--Fabbian Dufoe
  350 Ling-A-Mor Terrace South
  St. Petersburg, Florida  33705
  813-823-2350

UUCP: ...gatech!codas!usfvax2!jc3b21!fgd3