From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org, simo@redhat.com
Subject: Re: [PATCH] sunrpc: Add comment defining gssd upcall API keywords
Date: Mon, 20 Aug 2018 15:05:01 -0400 [thread overview]
Message-ID: <20180820190501.GC5468@fieldses.org> (raw)
In-Reply-To: <20180820143801.10060.61177.stgit@klimt.1015granger.net>
On Mon, Aug 20, 2018 at 10:39:16AM -0400, Chuck Lever wrote:
> During review, it was found that the target, service, and srchost
> keywords are easily conflated. Add an explainer.
>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> net/sunrpc/auth_gss/auth_gss.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> Hi Bruce-
>
> I've received no objections to this patch. Can you include it in
> v4.19 with the other patches I've already submitted?
Will do, it'll probably just be another week or so before I publish a
4.19 branch.
--b.
>
>
> diff --git a/net/sunrpc/auth_gss/auth_gss.c b/net/sunrpc/auth_gss/auth_gss.c
> index 1943e11..2460759 100644
> --- a/net/sunrpc/auth_gss/auth_gss.c
> +++ b/net/sunrpc/auth_gss/auth_gss.c
> @@ -461,12 +461,28 @@ static int gss_encode_v1_msg(struct gss_upcall_msg *gss_msg,
> buflen -= len;
> p += len;
> gss_msg->msg.len = len;
> +
> + /*
> + * target= is a full service principal that names the remote
> + * identity that we are authenticating to.
> + */
> if (target_name) {
> len = scnprintf(p, buflen, "target=%s ", target_name);
> buflen -= len;
> p += len;
> gss_msg->msg.len += len;
> }
> +
> + /*
> + * gssd uses service= and srchost= to select a matching key from
> + * the system's keytab to use as the source principal.
> + *
> + * service= is the service name part of the source principal,
> + * or "*" (meaning choose any).
> + *
> + * srchost= is the hostname part of the source principal. When
> + * not provided, gssd uses the local hostname.
> + */
> if (service_name) {
> char *c = strchr(service_name, '@');
>
> @@ -482,6 +498,7 @@ static int gss_encode_v1_msg(struct gss_upcall_msg *gss_msg,
> p += len;
> gss_msg->msg.len += len;
> }
> +
> if (mech->gm_upcall_enctypes) {
> len = scnprintf(p, buflen, "enctypes=%s ",
> mech->gm_upcall_enctypes);
prev parent reply other threads:[~2018-08-20 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 14:39 [PATCH] sunrpc: Add comment defining gssd upcall API keywords Chuck Lever
2018-08-20 15:55 ` Steve Dickson
2018-08-20 19:05 ` 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=20180820190501.GC5468@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=simo@redhat.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).