Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!agate!bionet!apple!bloom-beacon!tut.cis.ohio-state.edu!mailrus!ncar!umigw!umbio!jherr
From: jherr@umbio.MIAMI.EDU (Jack Herrington)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  RFC on Internet "Virus", Please
Message-ID: <881@umbio.MIAMI.EDU>
Date: 7 Nov 88 22:06:54 GMT
References: <8811071522.AA15390@csc-lons.arpa>
Lines: 16

in article <8811071522.AA15390@csc-lons.arpa>, scottr@CSC-LONS.ARPA (Scott W. Rogers) says:
> 
> One suggestion is not to place this RFC in the "public" domain, but to
> have some intity maintain it and only send it on request.  Possible
> checking out the 's credentials/identity of the requestor first!
>

If anything that would only make the hackers more intent on getting it and
using it, if we make it avaliable and say that making one would be 'passe' and
would be like repeating a bad joke twice, chances are half of the hackers
won't care enough to give it the time.

-Jack
 "Got any sweet n' low little fella?"
 "What--? Elvis?! Elvis Presley?!"
 "Mum's the work, I tired of the 15-hour workday of the Vegas Headliner..."
                                                          -Bloom County