Thanks to Jeff, who has definitely put me on the road to understanding
the problem and finding the culprit.  The two articles he cites from
1995 (his original post and Mike Paivinen's response) are very relevant.

I'm afraid there is still a bug where a RENAME attempt that fails for
security reasons may nevertheless cause an ACD to be attached to the
file.  That ACD can't perfectly represent the MPE security, so some
users may lose the ability to access the file.

Walter

Walter J. Murray


-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of Jeff Kell
Sent: Friday, February 03, 2006 8:25 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] Mystery ACDs

Rich Trapp wrote:
> Hey Walter :)
> 
> 
>    It's been awhile, but I think ACDs would be created if I copied
> and/or renamed files across accounts. 

There was an early 5.0 issue with :RENAMEing a file that you didn't own
(but had R/W access to).

I mentioned this in, umm, 1995 :-)

http://raven.utc.edu/cgi-bin/WA.EXE?A2=ind9501B&L=HP3000-L&P=R3175

and a Mike Paivinen follow-up:

http://raven.utc.edu/cgi-bin/WA.EXE?A2=ind9501C&L=HP3000-L&P=R979

Jeff

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *