From: Christian Fischer <Christian.Fischer@fischundfischer.com>
To: Frank van Maarseveen <frankvm@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS TUNING: #define NFS3_MAXGROUPS
Date: Mon, 27 Sep 2004 15:38:47 +0200 [thread overview]
Message-ID: <200409271538.47987.Christian.Fischer@fischundfischer.com> (raw)
In-Reply-To: <20040926222856.GA22758@janus>
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
On Monday 27 September 2004 00:28, Frank van Maarseveen wrote:
> That limit is hardcoded in the SUNRPC protocol (part of NFS) and
> _cannot_ be changed: it is a fundamental constant in NFS with AUTH_UNIX
> authentication. However, there is a trick to bypass this protocol
> limitation, see http://www.frankvm.com/nfs-ngroups for a 2.4.x patch.
>
> The 2.6.x patch is under development.
Thanks for this link. It isn't no more necessary to patch anything since i've
reduced the number of groups per uid to the limit. Well, i'd been reading the
sunRPC rfc before, bringing a lot of trouble to me.
The main problem was that users in the seventeenth (or higher) group (they
should not have any permissions for this group because of NFS_MAXGROUPS) were
able to change without permissions into those directories. I think a user or
group should have permission or NOT, and not a "bit of permissions".
Christian
root@terminalserver # ls -al /home/henry/shared/
[...]
drwxrws--- not_henry 17th_grp work
[...]
henry@terminalserver # cd /home/henry/shared/work/
henry@terminalserver work # ls
ls: reading directory .: Permission denied
# groups henry
[...] 17th_grp 18th_grp [...]
--
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2004-09-27 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-26 14:38 Christian Fischer
2004-09-26 14:43 ` Christian Fischer
2004-09-26 22:28 ` Frank van Maarseveen
2004-09-27 13:38 ` Christian Fischer [this message]
2004-09-26 16:10 ` Trond Myklebust
2004-09-26 16:25 ` Christian Fischer
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=200409271538.47987.Christian.Fischer@fischundfischer.com \
--to=christian.fischer@fischundfischer.com \
--cc=frankvm@xs4all.nl \
--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®