Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!cbosgd!ihnp4!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: Re: File Ownership
Message-ID: <9405@ucbvax.ARPA>
Date: Sun, 28-Jul-85 11:17:37 EDT
Article-I.D.: ucbvax.9405
Posted: Sun Jul 28 11:17:37 1985
Date-Received: Mon, 29-Jul-85 07:59:09 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 18

From: tencati@jpl-vlsi.arpa


Indeed VMS 4.1 assigns ownership of files based on who owns the directory they
are written to.  What I learned in DEC's 4.1 update seminar was that if you 
make [SAM] owned by an identifier, and the identifier has the /resource
qualifier, that whoever copies a file into that directory will retain ownership.
I'd have to look up the notes to see the details, but it was possible.  I asked
specifically about maintaining a [public] directory.  I did not want the system
to own the files, but I did want it to own the directory.  

Now that I think more on the subject, it wasn't the v4.1 upgrade seminar, it was
a DECUS pre-symposium seminar on security where we discussed this.

I hope I was of some help.  Contact me if you need more details.

Ron Tencati
TENCATI@JPL-VLSI.ARPA