From: Simo Sorce <simo@redhat.com>
To: jlayton@redhat.com
Cc: steved@redhat.com, linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] Fix credential sourcing with new setuid behavior in rpc.gssd
Date: Fri, 17 Jan 2014 11:56:38 -0500 [thread overview]
Message-ID: <1389977800-10922-1-git-send-email-simo@redhat.com> (raw)
In-Reply-To: <1389931919-4801-1-git-send-email-simo@redhat.com>
Take 3
Patch 1:
- simply remove the old code that is not necessary anymore
* removed an additional unused variable in take 3
Bonus patch 2:
- clean up code, name is not needed anymore as the default
credentials for the impersonated uid are always used.
* also stopped passing uid needlessly around in take 3
Pointed out by Steve, thanks.
Simo Sorce (2):
Improve first attempt at acquiring GSS credentials
Remove unused arguments
utils/gssd/gssd_proc.c | 2 +-
utils/gssd/krb5_util.c | 32 ++++++--------------------------
utils/gssd/krb5_util.h | 2 +-
3 files changed, 8 insertions(+), 28 deletions(-)
next prev parent reply other threads:[~2014-01-17 16:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 21:41 [PATCH] Fix crdential sourcing with new setuid behavior in rpc.gssd Simo Sorce
2014-01-16 15:47 ` Jeff Layton
2014-01-17 1:28 ` Simo Sorce
2014-01-17 1:49 ` Jeff Layton
2014-01-17 4:11 ` [PATCH 0/2] Fix credential " Simo Sorce
2014-01-17 4:11 ` [PATCH 1/2] Improve first attempt at acquiring GSS credentials Simo Sorce
2014-01-17 4:11 ` [PATCH 2/2] Remove unused parameter Simo Sorce
2014-01-17 11:54 ` [PATCH 0/2] Fix credential sourcing with new setuid behavior in rpc.gssd Jeff Layton
2014-01-17 16:56 ` Simo Sorce [this message]
2014-01-17 16:56 ` [PATCH 1/2] Improve first attempt at acquiring GSS credentials Simo Sorce
2014-01-17 16:56 ` [PATCH 2/2] Remove unused arguments Simo Sorce
2014-01-20 22:03 ` Steve Dickson
2014-01-20 22:03 ` [PATCH 1/2] Improve first attempt at acquiring GSS credentials 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=1389977800-10922-1-git-send-email-simo@redhat.com \
--to=simo@redhat.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@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