Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rochester!cornell!uw-beaver!mit-eddie!ll-xn!ames!ucbcad!ucbvax!RED.RUTGERS.EDU!AWalker
From: AWalker@RED.RUTGERS.EDU (*Hobbit*)
Newsgroups: comp.os.vms
Subject: ACLs
Message-ID: <12313671701.59.AWALKER@RED.RUTGERS.EDU>
Date: Fri, 26-Jun-87 18:18:52 EDT
Article-I.D.: RED.12313671701.59.AWALKER
Posted: Fri Jun 26 18:18:52 1987
Date-Received: Sun, 28-Jun-87 01:01:46 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 27

While digging around through various things with DUMP [which I do on
occasion] I stumbled on a whole slew of things that look like ACL keywords,
but there were a lot more of them than are documented.  Does anyone know
what things like

	bi_journal_name
	audit_journal
	size
	flags
	bit_6 [all the way up to bit_31]
	journaled_file
	marked_for_journaling
	hidden

are and what knows about them?  Putzing with SET ACL and such brought forth
continual refusal to do anything.

Side note:  Security audit alarms are a crock.  If I queue up a zillion
read QIOs to the OPCOM mailbox [I think it's usually MBA2], issue an innocuous
"request" to fill the one OPCOM already had outstanding, OPCOM isn't going to
see diddly for a good long time, while I'm turning off audits, messing with
symbionts, bouncing the network, romping through the UAF, etc.  A vague fix
for this would be to have OPCOM queue up a zillion reads, or use some othre
mechanism than a mailbox to handle $sndopr.

_H*
-------