From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: clifford@clifford.at (Clifford Wolf)
Cc: Remy.Card@linux.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Ext2FS: SUID on Dir
Date: Tue, 28 Aug 2001 11:49:25 -0400 (EDT) [thread overview]
Message-ID: <200108281549.f7SFnPg263571@saturn.cs.uml.edu> (raw)
In-Reply-To: <Pine.LNX.4.33.0108281227280.1127-100000@nerd.clifford.at> from "Clifford Wolf" at Aug 28, 2001 12:52:46 PM
Clifford Wolf writes:
> As you all know, on Ext2FS Partitions the SGID flag has a special function
> on directories: files within that directories will be owned by the same
> group that also owns the directory - which is useful for creating
> directories which are shared between the members of a group.
>
> 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 ...
>
> 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. So, if one sets both - SUID and SGID - on a directory, it
> will also work with a umask like 022 or 077 and there is no more need for
> an extra group for every user.
It would at least be more logical to have SUID do for user IDs
what SGID does for group IDs. Having SUID muck with group IDs
is pretty ugly.
next prev parent reply other threads:[~2001-08-28 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-28 10:52 Clifford Wolf
2001-08-28 11:18 ` Jamie Lokier
2001-08-28 15:49 ` Albert D. Cahalan [this message]
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=200108281549.f7SFnPg263571@saturn.cs.uml.edu \
--to=acahalan@cs.uml.edu \
--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
all inboxes | Powered by JetHome®