From: Steve Dickson <SteveD@redhat.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: ssorce@redhat.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v3 1/2] gssd: have process_krb5_upcall fork before handling upcall
Date: Mon, 21 Oct 2013 13:30:22 -0400 [thread overview]
Message-ID: <526564AE.3010507@RedHat.com> (raw)
In-Reply-To: <1381350116-10464-2-git-send-email-jlayton@redhat.com>
On 09/10/13 16:21, Jeff Layton wrote:
> Most krb5 installations use credcache locations that contain %{uid},
> which expands to the real UID of the current process. In order for
> GSSAPI to find those properly, we need to be able to switch the real UID
> of the process to the designated one. That however, opens the door to
> allowing gssd to be killed or reniced during the window where we've
> switched credentials.
>
> To combat this, change gssd to fork before trying to handle each upcall.
> The child will do the work to establish the context and the parent task
> will just wait for it to exit. It's still possible for the child to be
> killed or reniced, but that would only affect a single upcall instead of
> the entire daemon. Also, If the process is killed prematurely, then log
> an error to tip off the admin that there was a problem.
>
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
Committed...
steved.
> ---
> utils/gssd/gssd_proc.c | 24 +++++++++++++++++++++++-
> 1 file changed, 23 insertions(+), 1 deletion(-)
>
> diff --git a/utils/gssd/gssd_proc.c b/utils/gssd/gssd_proc.c
> index e58c341..99537d9 100644
> --- a/utils/gssd/gssd_proc.c
> +++ b/utils/gssd/gssd_proc.c
> @@ -67,6 +67,8 @@
> #include <errno.h>
> #include <gssapi/gssapi.h>
> #include <netdb.h>
> +#include <sys/types.h>
> +#include <sys/wait.h>
>
> #include "gssd.h"
> #include "err_util.h"
> @@ -982,6 +984,26 @@ process_krb5_upcall(struct clnt_info *clp, uid_t uid, int fd, char *tgtname,
> int err, downcall_err = -EACCES;
> gss_cred_id_t gss_cred;
> OM_uint32 maj_stat, min_stat, lifetime_rec;
> + pid_t pid;
> +
> + pid = fork();
> + switch(pid) {
> + case 0:
> + /* Child: fall through to rest of function */
> + break;
> + case -1:
> + /* fork() failed! */
> + printerr(0, "WARNING: unable to fork() to handle upcall: %s\n",
> + strerror(errno));
> + return;
> + default:
> + /* Parent: just wait on child to exit and return */
> + wait(&err);
> + if (WIFSIGNALED(err))
> + printerr(0, "WARNING: forked child was killed with signal %d\n",
> + WTERMSIG(err));
> + return;
> + }
>
> printerr(1, "handling krb5 upcall (%s)\n", clp->dirname);
>
> @@ -1121,7 +1143,7 @@ out:
> AUTH_DESTROY(auth);
> if (rpc_clnt)
> clnt_destroy(rpc_clnt);
> - return;
> + exit(0);
>
> out_return_error:
> do_error_downcall(fd, uid, downcall_err);
>
next prev parent reply other threads:[~2013-10-21 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 20:21 [PATCH v3 0/2] gssd: allow gssd to work with KEYRING: credcaches Jeff Layton
2013-10-09 20:21 ` [PATCH v3 1/2] gssd: have process_krb5_upcall fork before handling upcall Jeff Layton
2013-10-21 17:30 ` Steve Dickson [this message]
2013-10-09 20:21 ` [PATCH v3 2/2] gssd: do a more thorough change of identity after forking Jeff Layton
2013-10-21 17:30 ` Steve Dickson
2013-10-15 13:34 ` [PATCH v3 0/2] gssd: allow gssd to work with KEYRING: credcaches Jeff Layton
2013-10-16 12:22 ` Steve Dickson
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=526564AE.3010507@RedHat.com \
--to=steved@redhat.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=ssorce@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 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.