From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kevin Coffman <kwc@citi.umich.edu>
Cc: Valentijn Sessink <valentyn@blub.net>, linux-nfs@vger.kernel.org
Subject: Re: no_root_squash (and valid KRB root-ticket)
Date: Thu, 18 Nov 2010 12:46:04 -0500 [thread overview]
Message-ID: <20101118174603.GB28975@fieldses.org> (raw)
In-Reply-To: <AANLkTinS4mYVM1aA+-dkb_Q2m3Gz+TVmVPcBBOgAByqf@mail.gmail.com>
On Thu, Nov 18, 2010 at 10:27:02AM -0500, Kevin Coffman wrote:
> On Thu, Nov 18, 2010 at 10:07 AM, Valentijn Sessink <valentyn@blub.net> wrote:
> > Hi Kevin,
> >
> > Kevin Coffman schreef:
> >>>> 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.)
> >>> 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)
> >
> > It used to be, when local UID = server UID was the fine way of
> > authenticating - but with KRB authentication, the idea is that you
> > authenticate to the server.
> >
> > To summarize: when your UID=0 on the client, you cannot be root at the
> > server, because UID=0 is handled differently by gssd.
>
> Actually, in the case of UID=0, the client's machine credentials are
> used. You can map that Kerberos principal to root on the server. So
> this _is_ possible.
Also, the kernel and the gssd upcall should distinguish between
"machine" and "root" now. I don't know if gssd's using that
information.
--b.
>
> > If you have any
> > other UID, you can map this to UID=0 on the server - either by using
> > "kinit root" at the client, or by setting up a specific mapping for
> > libnfsidmap.
>
> Creating a "root" Kerberos principal is discouraged. (You might,
> however, have a "root/<fqdn>" principal -- that you could use for
> machine credentials.)
>
> K.C.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-11-18 17:46 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
2010-11-18 15:07 ` Valentijn Sessink
2010-11-18 15:27 ` Kevin Coffman
2010-11-18 17:46 ` J. Bruce Fields [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=20101118174603.GB28975@fieldses.org \
--to=bfields@fieldses.org \
--cc=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 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.