Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pacbell!sactoh0!americ!erk
From: erk@americ.UUCP (Erick Parsons)
Newsgroups: comp.sys.amiga
Subject: Re: Virus Protection ?
Message-ID: <1934.AA1934@americ>
Date: 12 Sep 89 20:26:47 GMT
Followup-To: comp.sys.amiga
Distribution: na
Lines: 37


->From: usenet@cps3xx.UUCP (Usenet file owner) Message-ID: <4562@cps3xx.UUCP>
-->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 !
-->
-->I got em in one swipe using the list lformat command:

->This would only fool brain-dead viruses.
->
->Any virus worth its bits would check this,
->de-protect what it needed too, and then reprotect
->and set-date so the only change visible would be
->the size of the file.

->FYI: A program can change file protection bits without using
->the c:protect program.
->REAL NAME: Joe Porkka   jap@frith.egr.msu.edu

Hmmm.. Seems to me that with a simple (?) OS mod we could have some sort
of Script Bit password protection as an option. I'm not a programmer so
I may be out in left field on this but the concept seems similiar to 
one that is already used on Unix systems. If it were possible would this
stand up to these killer viruses ?? .... Just wondering..


--
--
-------------------  // ----------------------------------------------------
 Erick Parsons      // .Knowledge is little more than  knowing the questions
 -------------     //  .erk@americ.UUCP or ..ames!pacbell!sactoh0!americ!erk
 Sacramento Ca \\ //   .GEnie: E.PARSONS      %-)       Hamatuer Radio N6RZB
--------------  \X/ --------------------------------------------------------