Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!dartvax!eleazar.dartmouth.edu!dav From: dav@eleazar.dartmouth.edu (William David Haas) Newsgroups: comp.sys.atari.st Subject: Re: Right of reply, virus- public, private- a thin line Message-ID: <12465@dartvax.Dartmouth.EDU> Date: 2 Mar 89 15:54:43 GMT References: <699@orbit.UUCP> <15139@cup.portal.com> <1200@hudson.acc.virginia.edu> <15225@cup.portal.com> Sender: news@dartvax.Dartmouth.EDU Reply-To: dav@eleazar.dartmouth.edu (William David Haas) Organization: Dartmouth College, Hanover, NH Lines: 27 In article <15225@cup.portal.com> Bob_BobR_Retelle@cup.portal.com writes: >Greg Lindahl writes that he was able to write a virus detecting ACCessory >from a description of a virus... > >That's great, and Greg's ACCessory may be able to help a lot of others to >check out their disks... but... Greg and others here are in the minority >when considered against the larger body of ST *users* to whom a description >of a virus would be largely "Greek". To them, the information would be >practically worthless, other than to alert them that such things are >possible.. I have no idea how to make a virus. I also have no idea how to stop one. If someone posted a virus I would not read it to learn how to stop so I could right my own. Why should I when there are great humanitarians like Greg L. running around (Thanks Greg!). On the other hand, I would like to see the code with an explanation of how it works just so I can learn a little about the subject. I wont be creating any vires (sp?) and I wont be creating any vaccination programs but I would like to know how they work. _ "Shadow, do something! Those flying Morpheous / \ birds are going to get us!" Psimon / _ \ shadow master / //\ \ "O.k., o.k., I'll cast Dav El II / // \\ \ Transmute Roc to mud." / /____\\ \ We are the /________\\ \ warrior spirit. \__________\/