Xref: utzoo comp.sys.atari.st:14201 comp.sys.apple:10238 comp.sys.mac:27143 comp.sys.ibm.pc:25096
Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!sun!pitstop!sundc!seismo!uunet!portal!cup.portal.com!Bob_BobR_Retelle
From: Bob_BobR_Retelle@cup.portal.com
Newsgroups: comp.sys.atari.st,comp.sys.apple,comp.sys.mac,comp.sys.ibm.pc
Subject: Re: Right of reply, virus- public, private- a thin line
Message-ID: <14940@cup.portal.com>
Date: 22 Feb 89 06:33:05 GMT
References: <415@odin.cs.hw.ac.uk>
Organization: The Portal System (TM)
Lines: 22

I agree that this is a sensitive matter...  the  *ONLY*  time I ever tried
to surpress any Topic of discussion on GEnie was when the discussion of 
"Trojan Horses" got too close to discussing  ACTUAL  methods of destructive
programming..  (the term "virus" hadn't yet entered into things..)
 
I didn't want my Roundtable to be the inspiration for some 16-year old
"hacker" to "make a name for himself" by using the information in a 
destructive manner...  
 
I did take some flak in the interests of "Freedom of Speech", but in this
case I felt it was justified...
 
Where do you draw the line...?   Are we better prepared if we see what most
destructive programs look like..?  Or...  can we possibly avoid future
problems by surpressing this information now..?
 
I'd like to see the source code for these "viruses", but who's to believe
that *I* won't use them destructively...?
 
No answers, I'm afraid...
 
BobR