Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!watmath!clyde!cbosgd!ulysses!ucbvax!te.cc.cmu.edu!EC0N
From: EC0N@TE.CC.CMU.EDU (Eric R. Crane)
Newsgroups: mod.computers.vax
Subject: Security issues
Message-ID: <8511122219.AA09348@ucbvax.berkeley.edu>
Date: Tue, 12-Nov-85 16:31:02 EST
Article-I.D.: ucbvax.8511122219.AA09348
Posted: Tue Nov 12 16:31:02 1985
Date-Received: Fri, 15-Nov-85 04:02:23 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 13
Approved: info-vax@ucbvax.berkeley.edu

One solution might be to do something similar to what was done with the
Tops-20 mailing list.  Create a subset of INFO-VAX which contains only
system managers.   Then if someone has a security issue they send it
to something like INFO-VAX-SECURE.  The only way that the problem can
be solved is to split the list.

No matter how freely we want information to flow the first time that my
systems crash because someone decided to play around with something that
they saw on the list I will be a bit upset.  I think that this goes for
most people out there.

- Eric Crane
-------