From: "J. Bruce Fields" <bfields@fieldses.org>
To: paul.szabo@sydney.edu.au
Cc: neilb@suse.de, linux-nfs@vger.kernel.org
Subject: Re: Please support NSF squashing multiple groups
Date: Fri, 19 Aug 2011 15:19:45 -0400 [thread overview]
Message-ID: <20110819191945.GA1641@fieldses.org> (raw)
In-Reply-To: <201108190210.p7J2AYCB028893@bari.maths.usyd.edu.au>
On Fri, Aug 19, 2011 at 12:10:34PM +1000, paul.szabo@sydney.edu.au wrote:
> > If you are using kerberos authentication then you should be able
> > to trust that any remote user really is who they say they are ...
>
> Does that "work" also against the "evil remote root" e.g. when the
> remote machine is compromised?
It does what's possible. If a user gives their credentials to the
compromised client--well, what can you do, the attacker has their
credentials at that point. So if everyone in your department logs into
the same client, then root on that client is going to be able to
impersonate any of them. Nothing you can do about that.
On the other hand, if several people each have their own client and only
log in to their own clients, and if one of the clients is compromised,
then that client isn't going to be able to impersonate users that have
never given it any credentials.
> > If you are using NFSv4 and kerberos than there already exist
> > interfaces to do what you want. See "man idmap.conf". ...
>
> Sorry I do not use NFSv4 or kerberos, yet. Could you please point me
> to references about idmap.conf, the ones I found suggest it only takes
> [Mapping] settings for Nobody-User and Nobody-Group.
Look for "static" in a recent version of the idmapd.conf man page.
--b.
next prev parent reply other threads:[~2011-08-19 19:19 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
2011-08-19 2:10 ` paul.szabo
2011-08-19 19:19 ` J. Bruce Fields [this message]
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=20110819191945.GA1641@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--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.