Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!lll-winken!iggy.GW.Vitalink.COM!widener!netnews.upenn.edu!vax1.cc.lehigh.edu!cert.sei.cmu.edu!krvw
From: ethan@thinc.COM (Ethan.Lish@THINC.COM)
Newsgroups: comp.virus
Subject: Re: UNIX & Viruses (UNIX)
Message-ID: <0009.9104101917.AA00785@ubu.cert.sei.cmu.edu>
Date: 10 Apr 91 12:25:22 GMT
Sender: Virus Discussion List <VIRUS-L@LEHIIBM1>
Lines: 33
Approved: krvw@sei.cmu.edu

padgett%tccslr.dnet@uvs1.orl.mmc.com (A. Padgett Peterson) writes:

Greetings -

	In continuation of the *NIX Virus Thread I would like a add a
	few points.  First off I would like to direct you to
	'Computer Systems' Volume 2 Spring 1989, Experiences with
	Viruses on *NIX Systems and Virology 101

> Basically, the sheer diversity of UNIX platforms provides the best
> defense against malicious software. Mix in the user/kernel and
> "rights" requirements and you have the basis for a good protection
> scheme.

	This is correct if your virus model excludes the shell script
	world. I have not seen *any* published model to define a virus
	vs Trojan Horse in the group. Was one published and I missed it?

	The simplest form of a *NIX virus is :

			cp $0 .

	Now *every* *NIX platform I know of will run this "virus"

		Thanks,
			\Ethan\

P.S. **NOTE DO NOT RUN THIS VIRUS, SO I DON'T HAVE TO SAY "I TOLD YOU SO"**
- --
     "If everyone swept his own doorstep, the whole world would be clean"
                           A Chinese proverb
  Ethan.Lish@THINC.COM _____ 1.301.652.0651 _____ {uunet,anagld}!thinc!ethan
  Tomorrow's Horizons, Inc. 4807 Bethesda Ave, #330, Bethesda, MD 20814-5299