Path: utzoo!attcan!uunet!ns-mx!iowasp!deimos!ux1.cso.uiuc.edu!brutus.cs.uiuc.edu!rpi!uwm.edu!psuvax1!rutgers!netnews.upenn.edu!vax1.cc.lehigh.edu!sei.cmu.edu!krvw From: jg3o+@andrew.cmu.edu (Jason Ari Goldstein) Newsgroups: comp.virus Subject: Idea for WDEF Innoculation (Mac) Message-ID: <0003.9002071838.AA05671@ge.sei.cmu.edu> Date: 6 Feb 90 17:23:51 GMT Sender: Virus Discussion List Lines: 33 Approved: krvw@sei.cmu.edu Just like everywhere else the WDEF is thriving here at Carnegie-Mellon Univ. I recently removed WDEF A & B off of 15 disks of a friend of mine. When I commented to somone here about the virus they said there was nothing they could do to stop it, except remove it once a machine got infected. I don't know much about Macs (Being a PC person) but if I understand correctly every time the disk is inserted the they Virus is sread to the disk. Well, why doesn't someone write an innoculation directly based on the virus itself. Everytime a disk is inserted in the drive it would be checked for infection if so it would remove WDEF if not it would then 'innoculate the disk' with itself. Eventually, WDEF would be wiped out the same way it was spread initially. The only problem with this is that it is a virus also, but with the proper prompts (allowing the user the choice of being innoculated) I don't think this would be a problem. I know I would mind not ever being infected by a virus that kills other viruses. In the mean time, about 75% of the time I in a cluster I remove WDEF A or B from either a hard disk or someone elses floppies. Later... me - ------------------- Jason Goldstein Internet: jg3o+@andrew.cmu.edu Disclaimer: I represent me and only me not CMU, not my folks, not anyone. "Thank the lord my PC came in the mail yesterday" - me Over, Finished, Gone, Done, Out.