From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Frank van Maarseveen <frankvm@frankvm.com>
Cc: Linux NFS mailing list <nfs@lists.sourceforge.net>
Subject: Re: NGROUPS limitation on RPCSEC_GSS/krb5?
Date: Thu, 24 Aug 2006 12:03:58 -0400 [thread overview]
Message-ID: <1156435438.5629.44.camel@localhost> (raw)
In-Reply-To: <20060824141428.GA23025@janus>
On Thu, 2006-08-24 at 16:14 +0200, Frank van Maarseveen wrote:
> I got a report from someone that RPCSEC_GSS/krb5 has a limit on the
> number of secondary groups: no more than 32 groups are supported.
>
> Can anyone confirm this?
<resending from a different account 'cos sourceforge apparently trusts
spamcop these days>
There is no reason why this limitation should exist, so that would have
to be an implementation "bug" in nfsd if true.
Hrmm... The kernel looks OK: the downcall stuff doesn't appear to be
limited.
...Ah. svcgssd appears to be using the NGROUPS macro. If your glibc is
old enough, then I suspect it might be setting that to 32, but at least
in my glibc, then /usr/include/sys/param.h would appear to be setting it
to NGROUPS_MAX, which again appears to evaluate to 65536.
Cheers,
Trond
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2006-08-24 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 14:14 NGROUPS limitation on RPCSEC_GSS/krb5? Frank van Maarseveen
2006-08-24 16:03 ` Trond Myklebust [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=1156435438.5629.44.camel@localhost \
--to=trond.myklebust@netapp.com \
--cc=frankvm@frankvm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.