Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!husc6!tut.cis.ohio-state.edu!ketch.cis.ohio-state.edu!martens
From: martens@ketch.cis.ohio-state.edu (Jeff Martens)
Newsgroups: comp.sys.amiga
Subject: Re: Virus Protection ?
Message-ID: <60226@tut.cis.ohio-state.edu>
Date: 11 Sep 89 20:06:32 GMT
References: <1894.AA1894@americ>
Sender: news@tut.cis.ohio-state.edu
Reply-To: Jeff Martens <martens@cis.ohio-state.edu>
Organization: Ohio State University Computer and Information Science
Lines: 17

In article <1894.AA1894@americ> erk@americ.UUCP (Erick Parsons) writes:

>With all of the occasional hoopla concerning virus's that add X # bytes to 
>random executables in your C directory why not take some VERY simple pre-
>cautions. Use those script bits. I've gone through my whole C directory and
>changed the script bits to ----r-e-. This should alert me to any phenomonem
>that would cause a write to those files and protect the files to boot !

This is probably worth doing, but note that it's only effective
against viruses that go through the OS to do their I/O.  Additionally,
a bright virus could look to see what the protection is initially,
change it to something writeable, and then restore the old protection
after making its changes.
-=-
-- Jeff (martens@cis.ohio-state.edu)

Ever seen a sparrow stall?