From: Steve Dickson <SteveD@redhat.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: trond.myklebust@primarydata.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 5/5] gssd: scrape the acceptor name out of the context
Date: Mon, 14 Apr 2014 11:07:37 -0400 [thread overview]
Message-ID: <534BF9B9.3000707@RedHat.com> (raw)
In-Reply-To: <1397161863-29266-6-git-send-email-jlayton@redhat.com>
Hey Jeff,
Just a couple nit....
On 04/10/2014 04:31 PM, Jeff Layton wrote:
> ...and pass it to the kernel in the downcall. Legacy kernels will just
> ignore the extra data, but with a proposed kernel patch the kernel will
> grab this info and use it to verify requests on the v4.0 callback
> channel.
>
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
> ---
> utils/gssd/gssd_proc.c | 39 ++++++++++++++++++++++++++++-----------
> 1 file changed, 28 insertions(+), 11 deletions(-)
>
> diff --git a/utils/gssd/gssd_proc.c b/utils/gssd/gssd_proc.c
> index 7387cce010cf..d95e39416c28 100644
> --- a/utils/gssd/gssd_proc.c
> +++ b/utils/gssd/gssd_proc.c
> @@ -77,6 +77,7 @@
> #include "context.h"
> #include "nfsrpc.h"
> #include "nfslib.h"
> +#include "gss_names.h"
>
> /*
> * pollarray:
> @@ -683,16 +684,19 @@ parse_enctypes(char *enctypes)
>
> static void
> do_downcall(int k5_fd, uid_t uid, struct authgss_private_data *pd,
> - gss_buffer_desc *context_token, OM_uint32 lifetime_rec)
> + gss_buffer_desc *context_token, OM_uint32 lifetime_rec,
> + gss_buffer_desc *acceptor)
> {
> char *buf = NULL, *p = NULL, *end = NULL;
> unsigned int timeout = context_timeout;
> unsigned int buf_size = 0;
>
> - printerr(1, "doing downcall lifetime_rec %u\n", lifetime_rec);
> + printerr(1, "doing downcall: lifetime_rec=%u acceptor=%.*s\n",
> + lifetime_rec, acceptor->length, acceptor->value);
> buf_size = sizeof(uid) + sizeof(timeout) + sizeof(pd->pd_seq_win) +
> sizeof(pd->pd_ctx_hndl.length) + pd->pd_ctx_hndl.length +
> - sizeof(context_token->length) + context_token->length;
> + sizeof(context_token->length) + context_token->length +
> + acceptor->length;
> p = buf = malloc(buf_size);
> if (!buf)
> goto out_err;
> @@ -707,6 +711,8 @@ do_downcall(int k5_fd, uid_t uid, struct authgss_private_data *pd,
> if (WRITE_BYTES(&p, end, pd->pd_seq_win)) goto out_err;
> if (write_buffer(&p, end, &pd->pd_ctx_hndl)) goto out_err;
> if (write_buffer(&p, end, context_token)) goto out_err;
> + if (acceptor->length > 0 &&
> + write_buffer(&p, end, acceptor)) goto out_err;
>
> if (write(k5_fd, buf, p - buf) < p - buf) goto out_err;
> free(buf);
> @@ -1034,6 +1040,9 @@ process_krb5_upcall(struct clnt_info *clp, uid_t uid, int fd, char *tgtname,
> gss_cred_id_t gss_cred;
> OM_uint32 maj_stat, min_stat, lifetime_rec;
> pid_t pid;
> + gss_name_t gacceptor;
> + gss_OID mech;
> + gss_buffer_desc acceptor = {0};
>
> pid = fork();
> switch(pid) {
> @@ -1174,15 +1183,22 @@ process_krb5_upcall(struct clnt_info *clp, uid_t uid, int fd, char *tgtname,
> goto out_return_error;
> }
>
> - /* Grab the context lifetime to pass to the kernel. lifetime_rec
> - * is set to zero on error */
Why get rid of this comment instead of updating it?
> - maj_stat = gss_inquire_context(&min_stat, pd.pd_ctx, NULL, NULL,
> - &lifetime_rec, NULL, NULL, NULL, NULL);
> + maj_stat = gss_inquire_context(&min_stat, pd.pd_ctx, NULL, &gacceptor,
> + &lifetime_rec, &mech, NULL, NULL, NULL);
>
> - if (maj_stat)
> - printerr(1, "WARNING: Failed to inquire context for lifetme "
> - "maj_stat %u\n", maj_stat);
> + if (maj_stat != GSS_S_COMPLETE) {
> + printerr(1, "WARNING: Failed to inquire context "
> + "maj_stat (0x%x)\n", maj_stat);
> + } else {
> + get_hostbased_client_buffer(gacceptor, mech, &acceptor);
> + gss_release_name(&min_stat, &gacceptor);
> + }
>
> + /*
> + * The serialization can mean turning the ctx into a lucid context. If
> + * that happens then the original ctx is no longer valid, so we mustn't
> + * try to use if after this point.
I'm not sure what you are trying to say here...
steved.
> + */
> if (serialize_context_for_kernel(&pd.pd_ctx, &token, &krb5oid, NULL)) {
> printerr(0, "WARNING: Failed to serialize krb5 context for "
> "user with uid %d for server %s\n",
> @@ -1190,9 +1206,10 @@ process_krb5_upcall(struct clnt_info *clp, uid_t uid, int fd, char *tgtname,
> goto out_return_error;
> }
>
> - do_downcall(fd, uid, &pd, &token, lifetime_rec);
> + do_downcall(fd, uid, &pd, &token, lifetime_rec, &acceptor);
>
> out:
> + gss_release_buffer(&min_stat, &acceptor);
> if (token.value)
> free(token.value);
> #ifdef HAVE_AUTHGSS_FREE_PRIVATE_DATA
>
next prev parent reply other threads:[~2014-04-14 15:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 20:30 [PATCH 0/5] gssd: add the GSSAPI acceptor name to the info passed in downcall Jeff Layton
2014-04-10 20:30 ` [PATCH 1/5] gssd: handle malloc failure appropriately in do_downcall Jeff Layton
2014-04-10 20:31 ` [PATCH 2/5] gssd: make do_downcall a void return Jeff Layton
2014-04-10 20:31 ` [PATCH 3/5] gssd: move hostbased name routines into separate file Jeff Layton
2014-04-10 20:31 ` [PATCH 4/5] gssd: add new routine for generating a hostbased principal in a gss_buffer_t Jeff Layton
2014-04-10 20:31 ` [PATCH 5/5] gssd: scrape the acceptor name out of the context Jeff Layton
2014-04-11 11:04 ` Jeff Layton
2014-04-14 15:07 ` Steve Dickson [this message]
2014-04-14 15:48 ` Jeff Layton
2014-04-14 18:09 ` Steve Dickson
2014-04-14 18:36 ` Simo Sorce
2014-04-14 18:44 ` Jeff Layton
2014-04-14 18:45 ` Simo Sorce
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=534BF9B9.3000707@RedHat.com \
--to=steved@redhat.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--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 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.