linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clifford Wolf <clifford@clifford.at>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: <Remy.Card@linux.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Ext2FS: SUID on Dir
Date: Tue, 28 Aug 2001 20:04:32 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0108281959040.11558-100000@nerd.clifford.at> (raw)
In-Reply-To: <200108281549.f7SFnPg263571@saturn.cs.uml.edu>

Hi,

> It would at least be more logical to have SUID do for user IDs
> what SGID does for group IDs.

Maybe - but at least I can't thing of any situation where that could be
needed.

> Having SUID muck with group IDs is pretty ugly.

It doesn't. It "mucks" with the group field in the file mode, it doesn't
do anything to the group id.

To be more exact: It copies the permissions from the user field in the
file mode to the group field in the file mode. Imo that is not far away
from the meaning of a SUID bit on programms: It gives the rights from the
user who owns the file to a wider range of users ..

yours,
 - clifford

--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
Clifford Wolf ................ www.clifford.at         IRC: http://opirc.nu
The ROCK Projects Workgroup .. www.rock-projects.com  Tel: +43-699-10063494
The ROCK Linux Workgroup ..... www.rocklinux.org      Fax: +43-2235-42788-4
The NTx Consulting Group ..... www.ntx.at            email: god@clifford.at

Reality corrupted. Reboot universe? (Y/N)                 www.rocklinux.net


      reply	other threads:[~2001-08-28 18:00 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
2001-08-28 15:49 ` Albert D. Cahalan
2001-08-28 18:04   ` Clifford Wolf [this message]

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=Pine.LNX.4.33.0108281959040.11558-100000@nerd.clifford.at \
    --to=clifford@clifford.at \
    --cc=Remy.Card@linux.org \
    --cc=acahalan@cs.uml.edu \
    --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).