[ From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX"  3-JAN-1991 22:28:15.02  To:	MRGATE::"ARISIA::EVERHART" CC:	 Subj:	RE: ACLs and Directories  * Received:  by crdgw1.ge.com (5.57/GE 1.80)( 	 id AA08956; Thu, 3 Jan 91 22:11:53 EST/ Message-Id:  <9101040311.AA08956@crdgw1.ge.com> W Received: From SCFD.NWC.NAVY.MIL by CRVAX.SRI.COM with TCP; Thu,  3 JAN 91 14:07:40 PST  Date: 3 Jan 91 13:40:00 PDT = From: "GSSF::GOPPELT" <goppelt%gssf.decnet@scfd.nwc.navy.mil> ! Subject: RE: ACLs and Directories ! To: "info-vax" <info-vax@sri.com>   * Jerry Leichter <leichter@LRW.COM> writes :   [...stuff deleted...]   O > If the point of adding the ACE's is to prevent users from making their file's P > shareable - forget it.  They can change the ACE's as easily as they change theP > SOGW protection mask.  The standard VMS access control system provides what isN > called "discretionary control":  The owner of an object has absolute control% > over who he lets have access to it.   O What about the OPTIONS=HIDDEN+PROTECTED in the ACE?  Example, add the following K ACE to a scratch file using the EDIT/ACL editor (you'll see why I suggest a  scratch file later) :   : 	(IDENTIFIER=NETWORK,OPTIONS=HIDDEN+PROTECTED,ACCESS=NONE)  K The HIDDEN option prevents a user from viewing the ACE unless they have the M SECURITY privilege (you won't be able to see it with the DIR/SECURITY or SHOW M ACL commands unless you have SECURITY enabled).  PROTECTED means that the ACE L will be preserved when an attempt is made to delete the entire ACL (i.e. SET3 ACL/DELETE will not delete a PROTECTED ACE, but SET J ACL/DELETE/ACL=(specified-ace) will - or you can delete it in the EDIT/ACL editor.)  O Now I've found that I can only add a HIDDEN ACE with the EDIT/ACL editor, *not* M with the SET ACL command.  I can delete a HIDDEN ACE with the SET ACL/DELETE, 5 but *not* with the EDIT/ACL.  (I'm running VMS V5.4.)   L A PROTECTED ACE can be added, or deleted with the proper SET ACL or EDIT/ACL	 commands.   G But a HIDDEN+PROTECTED ACE can only be created with the EDIT/ACL and it 7 *cannot* be deleted!  SET ACL/DELETE doesn't do it, SET O ACL/DELETE/ACL=(specified-ace) doesn't do it, EDIT/ACL and trying it from there O doesn't do it either.  In short, you can't get rid of it!  (Now aren't you glad M you tried this on a scratch file?)  If you delete the file, obviously it goes  away.   K So it would seem "possible" to add a security access measure, that the user N cannot remove.  But my advice?  STAY AWAY FROM IT.  I don't like the idea of a3 protection measure on files that CANNOT be removed.   N (You could COPY the file and delete the original, providing of course that theO ACEs aren't being propagated by a subdirectory with the OPTIONS=DEFAULT set.  I 1 can see a very troublesome configuration here...)    Jerry's advice of :   O > Create a comprehensive security policy.  Put IN WRITING what the goals of the K > policy are:  Who is to be allowed access to what, who is to be allowed to J > control what.  Make sure everyone involved understands the policy and is > satisfied with it.  
 is excellent.    				daveN ------------------------------------------------------------------------------N |David S. Goppelt          |Internet: goppelt%gssf.decnet@nwc.navy.mil       |N |Naval Weapons Center      |          goppelt%gssf.decnet@26.3.0.85          |N |China Lake, CA  93555  USA|Or:       goppelt@nwc.navy.mil                   |N |(619) 939-5023 av 437-5023|-------------------------------------------------|N |                          |"I'm different than other people - pain hurts me"|N ------------------------------------------------------------------------------    