From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: Clifford Wolf <clifford@clifford.at>
Cc: Remy.Card@linux.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Ext2FS: SUID on Dir
Date: Tue, 28 Aug 2001 12:18:47 +0100 [thread overview]
Message-ID: <20010828121847.B9690@thefinal.cern.ch> (raw)
In-Reply-To: <Pine.LNX.4.33.0108281227280.1127-100000@nerd.clifford.at>
In-Reply-To: <Pine.LNX.4.33.0108281227280.1127-100000@nerd.clifford.at>; from clifford@clifford.at on Tue, Aug 28, 2001 at 12:52:46PM +0200
Clifford Wolf wrote:
> But that only makes sense if the umask is set to give full permissions to
> the group (e.g. 007 or 002). Noone would do that if there is a system-wide
> 'users' group - so some distributions add an extra group for every user
> which lets the /etc/group file grow very fast and makes the admins life
> harder ...
Concured. In my experience, "extra group for every user" doesn't work
with you're sharing over NFS with systems that don't use it. Which
means using a umask of 022 or 077, and that renders the SGID-directory
feature almost useless.
I've seen two problems result from this: user files created group
writable on the NFS server, when they should not be (a security
problem). And shared directories created non-group-writable, which
other group members cannot fix. (Only root can fix this).
For example where I work, some of the CVS directories cannot be checked
out because some directories, which should be group writable, are not.
> The following small patch adds a function to the SUID flag on directories.
> If the SUID flag is set for a diectory, all new files in that directory
> will get the same rights in the group-field as they have in their
> user-field.
Your patch does not fix the problem with CVS directories. In those,
directories need to be writable, but newly created user files should not
necessarily be group writable.
So I would suggest this behaviour:
sgid directory -> new subdirectories copy group umask from user umask
suid directory -> new non-directories copy group umask from user umask
Both these behaviours would be enabled by a mount option, preferably a
generic one.
cheers,
-- Jamie
next prev parent reply other threads:[~2001-08-28 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-28 10:52 [PATCH] Ext2FS: SUID on Dir Clifford Wolf
2001-08-28 11:18 ` Jamie Lokier [this message]
2001-08-28 15:49 ` Albert D. Cahalan
2001-08-28 18:04 ` Clifford Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010828121847.B9690@thefinal.cern.ch \
--to=lk@tantalophile.demon.co.uk \
--cc=Remy.Card@linux.org \
--cc=clifford@clifford.at \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).