From: "J. Bruce Fields" <bfields@fieldses.org>
To: Simo Sorce <simo@redhat.com>
Cc: Steve Dickson <SteveD@redhat.com>,
Noam Meltzer <noam@primarydata.com>,
linux-nfs@vger.kernel.org, sssd-devel@lists.fedorahosted.org
Subject: Re: [PATCH v2 0/5] NFSv4 rpc.idmapd plugin
Date: Thu, 13 Mar 2014 13:25:31 -0400 [thread overview]
Message-ID: <20140313172531.GA7124@fieldses.org> (raw)
In-Reply-To: <1394729939.32465.231.camel@willson.li.ssimo.org>
On Thu, Mar 13, 2014 at 12:58:59PM -0400, Simo Sorce wrote:
> On Thu, 2014-03-13 at 11:24 -0400, Steve Dickson wrote:
>
> > V4 servers now have an option of returning a uid string (aka "3606")
> > where the NFS client just converts that into the uid.
>
> Can the client tell the server *not to do that* ?
The client can use kerberos, in which case the server won't do that.
Other than that, no, the behavior can only be controlled by server-side
configuration.
--b.
next prev parent reply other threads:[~2014-03-13 17:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 7:37 [PATCH v2 0/5] NFSv4 rpc.idmapd plugin Noam Meltzer
2014-03-04 7:37 ` [PATCH v2 1/5] NEW CLIENT: plugin for NFSv4 rpc.idmapd Noam Meltzer
2014-03-04 7:37 ` [PATCH v2 2/5] NFSv4 client: (private) headers from libnfsidmap Noam Meltzer
2014-03-04 7:37 ` [PATCH v2 3/5] NFSv4 client: add to build system Noam Meltzer
2014-03-04 7:37 ` [PATCH v2 4/5] NFSv4 client: man page Noam Meltzer
2014-03-04 7:37 ` [PATCH v2 5/5] NFSv4 client: add to RPM spec Noam Meltzer
2014-03-13 15:24 ` [PATCH v2 0/5] NFSv4 rpc.idmapd plugin Steve Dickson
2014-03-13 16:58 ` Simo Sorce
2014-03-13 17:25 ` J. Bruce Fields [this message]
2014-03-13 17:41 ` Simo Sorce
[not found] ` <1394732462.32465.235.camel-Hs+ccMQdwurzDu64bZtGtWD2FQJk+8+b@public.gmane.org>
2014-03-20 7:33 ` Noam Meltzer
2014-03-20 13:49 ` Steve Dickson
2014-05-27 19:46 ` [SSSD] " Jakub Hrozek
2014-05-27 20:02 ` Simo Sorce
2014-03-20 7:36 ` Noam Meltzer
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=20140313172531.GA7124@fieldses.org \
--to=bfields@fieldses.org \
--cc=SteveD@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=noam@primarydata.com \
--cc=simo@redhat.com \
--cc=sssd-devel@lists.fedorahosted.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;
as well as URLs for NNTP newsgroup(s).