From: Jeff Layton <jlayton@redhat.com>
To: trond.myklebust@primarydata.com
Cc: steved@redhat.com, linux-nfs@vger.kernel.org
Subject: [PATCH 0/3] nfs: fix v4.0 callback channel auth failures
Date: Thu, 10 Apr 2014 16:29:48 -0400 [thread overview]
Message-ID: <1397161791-29144-1-git-send-email-jlayton@redhat.com> (raw)
Earlier this week, we had a lively discussion about how to fix the
bogus way that the callback channel tries to authenticate requests
coming in. The consensus was that the right approach is to save off
the acceptor name in a GSSAPI SETCLIENTID call, and then to compare
that to the initiator name in the callback requests.
This patchset is the kernel portion of that change. There is also
a companion patchset for gssd to make it pass the acceptor name
to the kernel in the downcall.
Jeff Layton (3):
auth_gss: fetch the acceptor name out of the downcall
sunrpc: add a new "stringify_acceptor" rpc_credop
nfs4: copy acceptor name from context to nfs_client
fs/nfs/callback.c | 12 ++++++
fs/nfs/client.c | 1 +
fs/nfs/nfs4proc.c | 30 ++++++++++++++-
include/linux/nfs_fs_sb.h | 1 +
include/linux/nfs_xdr.h | 1 +
include/linux/sunrpc/auth.h | 2 +
include/linux/sunrpc/auth_gss.h | 1 +
net/sunrpc/auth.c | 9 +++++
net/sunrpc/auth_gss/auth_gss.c | 82 +++++++++++++++++++++++++++++------------
9 files changed, 115 insertions(+), 24 deletions(-)
--
1.9.0
next reply other threads:[~2014-04-10 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 20:29 Jeff Layton [this message]
2014-04-10 20:29 ` [PATCH 1/3] auth_gss: fetch the acceptor name out of the downcall Jeff Layton
2014-04-10 20:29 ` [PATCH 2/3] sunrpc: add a new "stringify_acceptor" rpc_credop Jeff Layton
2014-04-10 20:29 ` [PATCH 3/3] nfs4: copy acceptor name from context to nfs_client Jeff Layton
2014-05-28 21:39 ` Trond Myklebust
2014-05-28 23:20 ` Jeff Layton
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=1397161791-29144-1-git-send-email-jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
--cc=trond.myklebust@primarydata.com \
/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).