Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!iuvax!pur-ee!uiucdcs!uiucdcsm!acheng
From: acheng@uiucdcsm.cs.uiuc.edu
Newsgroups: comp.unix.wizards
Subject: Re: umask and multiple groups
Message-ID: <9100007@uiucdcsm>
Date: Thu, 12-Nov-87 12:52:00 EST
Article-I.D.: uiucdcsm.9100007
Posted: Thu Nov 12 12:52:00 1987
Date-Received: Sun, 15-Nov-87 03:36:28 EST
References: <21241@cmcl2.NYU.EDU>
Lines: 26
Nf-ID: #R:cmcl2.NYU.EDU:21241:uiucdcsm:9100007:000:1351
Nf-From: uiucdcsm.cs.uiuc.edu!acheng    Nov 12 11:52:00 1987


>/* Written 10:04 pm  Nov  6, 1987 by flee@gondor.psu.edu in uiucdcsm:comp.unix.wizards */
>I think one obvious answer is to have a file inherit the protections of the
>directory it's created in (file_mode & ~umask & dir_mode); inheritance of
>protection, like inheritance of group.  Minimal disruption--no extra
>structures to worry about.

The mode of directory is usually quite different from its files.  For
one thing, all directories must have at least one x-bit on but most
files have all x-bits off.  If all created files inherite that x-bit,
am I up for suprises since I have "." at the beginning of my $PATH.
Other problems: /tmp is "rwxrwxrwx" but I definitely do not want all
my /tmp/* files to be other-writable.  Another case: I may make my
$HOME/bin to be other-searchable (i.e.  rwx--x--x) to share my
private tools with other users only if they know the exact name
without letting them browse through it.  But if the tool is a shell
script, the read-bit must be on.  Inheritance of mode from directory
will give more troubles than its worth.

----------------------------------------------------------------------
Albert Cheng
acheng@a.cs.uiuc.edu (ARPAnet or CSNET)		uiucdcs!acheng(USENET)
Dept. of Computer Science, Univ. of Illinois-Urbana,
Rm. 240, 1304 W. Springfield, Urbana, IL 61801, USA.

%%% THE ABOVE IS MY OPINION STOP %%%