From: NeilBrown <neilb@suse.de>
To: paul.szabo@sydney.edu.au
Cc: linux-nfs@vger.kernel.org
Subject: Re: Please support NSF squashing multiple groups
Date: Fri, 19 Aug 2011 11:05:36 +1000 [thread overview]
Message-ID: <20110819110536.1f0133c6@notabene.brown> (raw)
In-Reply-To: <201108190032.p7J0W3ZX030679@bari.maths.usyd.edu.au>
On Fri, 19 Aug 2011 10:32:03 +1000 paul.szabo@sydney.edu.au wrote:
> Dear Linux-NFS people,
>
> NFS has always had the root_squash option, to protect against a remote
> and possibly evil root. NFS should also protect all privileged, or at
> least all root-equivalent, UIDs and GIDs. Many UNIX distributions have
> root-equivalent GIDs, groups whose members could easily become root,
> some listed in http://bugs.debian.org/299007#219 .
>
> Currently, NFS has no ways to protect privileged UIDs and GIDs other
> than root himself. Such options should be implemented, to make NFS
> safer and more useful. As I understand it, the hold-up is not within
> NFS code, but with kernel interfaces not supporting lists of squashed
> entities. I am asking you to devise and implement such interfaces.
>
> References:
> http://bugs.debian.org/299007
> http://bugs.debian.org/384922
> http://bugs.debian.org/538392
> https://bugzilla.kernel.org/show_bug.cgi?id=14295
>
> Thanks, Paul
>
> Paul Szabo psz@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
> School of Mathematics and Statistics University of Sydney Australia
Hi Paul,
I would be much more inclined to go the other way and remove the root_squash
option so that nothing is squashed. It is not really a clever idea and
doesn't really do anything useful - partly because as you note there are
other uids that can be dangerous.
If you are using kerberos authentication then you should be able to trust
that any remote user really is who they say they are, and if you aren't then
maybe you should be .... we really are running out of excuses to use
kerberos and it is really quite easy (even I could set it up in half an
hour!).
If you are using NFSv4 and kerberos than there already exist interfaces to
do what you want. See "man idmap.conf". You can write a plugin that maps a
textual user or group name to a numeric id number. So you can squash
anything that you want to squash, and squash it in any way that you like.
Does that help?
NeilBrown
next prev parent reply other threads:[~2011-08-19 1:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 0:32 Please support NSF squashing multiple groups paul.szabo
2011-08-19 1:05 ` NeilBrown [this message]
2011-08-19 2:10 ` paul.szabo
2011-08-19 19:19 ` J. Bruce Fields
2011-08-19 22:06 ` paul.szabo
2011-08-19 22:15 ` Andy Adamson
2011-08-19 22:35 ` paul.szabo
2011-08-19 23:45 ` J. Bruce Fields
2011-08-20 0:19 ` NeilBrown
2011-08-22 14:23 ` Andy Adamson
2011-08-19 19:29 ` J. Bruce Fields
2011-08-19 22:21 ` paul.szabo
2011-08-22 16:14 ` Jim Rees
[not found] ` <20110822161413.GE2477-8f4Pc2RrbJmHXe+LvDLADg@public.gmane.org>
2011-08-22 21:05 ` paul.szabo-E0wInbZyfUpWG/WdbR7gnQ
-- strict thread matches above, loose matches on Subject: below --
2011-09-20 22:48 paul.szabo
2011-09-20 23:05 ` Trond Myklebust
2011-09-20 23:29 ` paul.szabo
2011-09-20 23:38 ` Myklebust, Trond
2011-09-21 0:09 ` paul.szabo
2011-09-21 4:16 ` Myklebust, Trond
2011-09-21 5:38 ` paul.szabo
2011-09-20 23:47 ` Myklebust, Trond
2011-09-30 4:08 paul.szabo
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=20110819110536.1f0133c6@notabene.brown \
--to=neilb@suse.de \
--cc=linux-nfs@vger.kernel.org \
--cc=paul.szabo@sydney.edu.au \
/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.