info-vax@ucbvax.ARPA (08/01/85)
From: Greg Christy <GC0H@CMU-CC-TE.ARPA> I have been experimenting with access control lists in version 4.1 of VMS and I am experiencing difficulty with the Alarm type ACE. Has anyone been able to get it to work? The documentation in the Guide to VAX/VMS System Security and the help within the ACL editor differ in their specification of the alarm ACE. The manual lists it as (ALARM=SECURITY,ACCESS=...) and help in the ACL editor it lists it as (ALARM_JOURNAL,ACCESS=...). Neither of these are accepted by the ACL editor when I try to exit. Anyone have any ideas? ------------ Greg Christy (gc0h@cmu-cc-te.arpa) System Software Carnegie-Mellon University -------
info-vax@ucbvax.ARPA (08/01/85)
From: Gail Rubin <grubin@bbn-spca> I agree with Kevin Carosso that you should try using the direct commands for setting ACE's, not the ACL editor. I was trying something with ACE's last week and couldn't get it to work through the ACL editor. When I called DEC Software Support, they basically told me to avoid using the editor unless my ACE's were very complicated. So try your 2 alternatives directly with SET FILE/ACL. -- Gail Rubin (grubin@bbn-spca or @bbn-unix)
info-vax@ucbvax.ARPA (08/07/85)
From: *Hobbit* <AWalker@RUTGERS.ARPA> If you successfully stick an ACL on a file and then do dir/acl on it, I believe that it shows up a (ALARM_JOURNAL=SECURITY,...). Typed in [as opposed to edited/acl] acl's seem to require a lot more characters of each funny keyword than what the normal DCL parser seems to consider unique; ie (ala=sec) might not work, whereas (alarm=security) will. Also keywords to SET AUDIT, if put in certain orders, are ignored. It's all somewhat reminiscent of spreading mousetraps all over your house... _H* -------