From: NeilBrown <neilb@suse.de>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NFS: Fix keytabless mounts
Date: Wed, 5 Jun 2013 11:39:32 +1000 [thread overview]
Message-ID: <20130605113932.2999cf8f@notabene.brown> (raw)
In-Reply-To: <20130605004523.14256.24793.stgit@seurat.1015granger.net>
[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]
On Tue, 04 Jun 2013 20:56:31 -0400 Chuck Lever <chuck.lever@oracle.com> wrote:
> Commit 05f4c350 "NFS: Discover NFSv4 server trunking when mounting"
> Fri Sep 14 17:24:32 2012 introduced Uniform Client String support,
> which forces our NFS client to establish a client ID immediately
> during a mount operation rather than waiting until a user wants to
> open a file.
>
> Normally machine credentials (eg. from a keytab) are used to perform
> a mount operation that is protected by Kerberos. Before 05f4c350,
> SETCLIENTID uses a machine credential, or falls back to a regular
> user's credential if no keytab is available.
>
> 05f4c350 seems to have broken the ability to mount with sec=krb5 on
> clients that don't have a keytab. Performing SETCLIENTID early
> means there may be no user credential to fall back on, since during
> system initialization no regular user has kinit'd yet.
>
> Typically, root is required to kinit in this situation anyway to
> make a sec=krb5 mount work. So, the kernel should try to use root's
> credential for lease management if there's no keytab.
>
> The new logic should cause the root credential to be tried only
> after both the machine cred and a user cred are found to be
> unavailable.
>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
>
> Hi Neil-
>
> Here's a wacky idea to continue our conversation. Tested just
> enough to confirm it may do something useful. Applies to 3.7.
> Something similar might work for 3.8 and 3.9.
>
Thanks Chuck! Looks interesting.
I'll see if I can get it tested by someone who actually depends on this
working. I'll let you know how it goes.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2013-06-05 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 0:56 [PATCH] NFS: Fix keytabless mounts Chuck Lever
2013-06-05 1:39 ` NeilBrown [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=20130605113932.2999cf8f@notabene.brown \
--to=neilb@suse.de \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.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).