Linux NFS development
 help / color / mirror / Atom feed
From: Olaf Kirch <okir@suse.de>
To: MeiJia <cfs_eric@yahoo.com.cn>
Cc: NFS-devel <nfs@lists.sourceforge.net>
Subject: Re: about group membership
Date: Tue, 11 May 2004 20:22:00 +0200	[thread overview]
Message-ID: <20040511182200.GA17246@suse.de> (raw)
In-Reply-To: <40A10989.80300@yahoo.com.cn>

On Tue, May 11, 2004 at 11:12:41AM -0600, MeiJia wrote:
> While i'm looking at the NFS (include v4), I didn't find any code which 
> handle supplement group membership issues. so I'm curious how could NFS 
> deal with following situations, or what's the plan to support:
>  - normal supplement groups

Supplementary groups are transported in the AUTH_UNIX credentials.
If you you use a different authentication flavor, supplementary
groups are usually retrieved from the password database.

>  - setuid binaries

Linux nfs normally uses the effective uid in any requests
(if credentials are available; which is not a given for all
auth flavors).

There is an option to fall back to the real uid in certain cases,
but that is really more of a hack.

>  - setgroups binaries

I think we just add the effective uid to the groups vector,
if it is different from the rgid.

Olaf

-- 
Olaf Kirch     |  The Hardware Gods hate me.
okir@suse.de   |
---------------+ 


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2004-05-11 18:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11 17:12 about group membership MeiJia
2004-05-11 18:22 ` Olaf Kirch [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=20040511182200.GA17246@suse.de \
    --to=okir@suse.de \
    --cc=cfs_eric@yahoo.com.cn \
    --cc=nfs@lists.sourceforge.net \
    /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