Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wasatch!cs.utah.edu!zeleznik
From: zeleznik%cs.utah.edu@wasatch.UUCP (Mike Zeleznik)
Newsgroups: comp.sys.apollo
Subject: protections and sr10.1
Message-ID: <1460@wasatch.UUCP>
Date: 29 Mar 89 20:41:57 GMT
Sender: news@wasatch.UUCP
Reply-To: zeleznik%cs.utah.edu@wasatch.UUCP (Mike Zeleznik)
Organization: University of Utah CS Dept
Lines: 32

Update/summary on open/closed protections on the AA node in sr10.*.

The MINST program for 10.1.m (68k) and 10.0.p (10k) has the OPEN/CLOSED
selection BACKWARDS!  Selecting CLOSED gives you an OPEN system, and
the reverse...  Later versions are said to be fixed (?)

Once installed as OPEN on my AA node, I could not get the OS on the AA
into a closed form.  However, from what I have heard, even if a source
AA node is open, you can correctly install a closed system to another
node.  I haven't tried this.

The only two ways I have found of locking down an open AA node are
1) set protections manually (either your own scripts or via inprot), or
2) re-invol and reinstall the OS, selecting an OPEN system.  I did the
latter and it worked okay, but is time consuming.  While some things
are obviously wrong (e.g., /com and /usr are world writable), at least
most of the files seem to be right.  It's a far cry better than before!

Apollo or ADUS have no available template files for INPROT. If anyone
(* hello, Apollo? *) gets around to putting them together, that would be
great.  

Apparently there is some mechanism for converting your old ACL templates
into inprot form, but I heard from someone who tried it that it didn't
work.

Mike

Michael Zeleznik              Computer Science Dept.
                              University of Utah
zeleznik@cs.utah.edu          Salt Lake City, UT  84112
                              (801) 581-5617