From: Kevin Coffman <kwc@citi.umich.edu>
To: Valentijn Sessink <valentyn@blub.net>
Cc: linux-nfs@vger.kernel.org
Subject: Re: no_root_squash (and valid KRB root-ticket)
Date: Thu, 18 Nov 2010 09:25:42 -0500 [thread overview]
Message-ID: <AANLkTiktXSPbVJg40-bmum39RNekn8aggnWUSPCYdRb9@mail.gmail.com> (raw)
In-Reply-To: <4CE4F910.4080601@blub.net>
On Thu, Nov 18, 2010 at 4:59 AM, Valentijn Sessink <valentyn@blub.net> wrote:
> Kevin Coffman schreef:
>> Did you see my message about "static" mapping for libnfsidmap?
>
> Yes, but it's scope was not immediately clear to me. Also, I couldn't
> find the mapping feature you were mentioning; but my idmapd man page
> comes from the nfs-common sources, while your idmapd.conf example (as
> you explained) comes from libnfsidmap.
>
>> On your server, you can map "host/client.machine@REALM" to root. (Or
>> "nfs/client.machine@REALM" or "root/client.machine@REALM", depending
>> on what key you have on the client.)
>
> OK, now I understand :) As far as I can see, that would mean that anyone
> with root rights on the client (thus being able to read the machine
> keys) would have root rights on the server share, wouldn't it?
Isn't that the equivalent of no_root_squash? (root on the client ==
root on the server)
You are free to map any principal to root on the server. It doesn't
have to be a client's machine credentials.
K.C.
next prev parent reply other threads:[~2010-11-18 14:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 14:27 no_root_squash (and valid KRB root-ticket) Valentijn Sessink
2010-11-16 18:30 ` J. Bruce Fields
2010-11-16 19:52 ` Valentijn Sessink
2010-11-16 23:54 ` Kevin Coffman
2010-11-17 10:51 ` Valentijn Sessink
2010-11-17 14:26 ` Kevin Coffman
2010-11-18 9:59 ` Valentijn Sessink
2010-11-18 14:25 ` Kevin Coffman [this message]
2010-11-18 15:07 ` Valentijn Sessink
2010-11-18 15:27 ` Kevin Coffman
2010-11-18 17:46 ` J. Bruce Fields
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=AANLkTiktXSPbVJg40-bmum39RNekn8aggnWUSPCYdRb9@mail.gmail.com \
--to=kwc@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=valentyn@blub.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;
as well as URLs for NNTP newsgroup(s).