From: Doug Nazar <nazard.michi@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: gssd picking wrong creds
Date: Sat, 03 Jul 2010 23:30:17 -0400 [thread overview]
Message-ID: <4C300049.7040603@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 282 bytes --]
I'm running rpc.gssd with the the -n option. Noticed that with the new
version it's now creating the machine cache file which is also owned by
root so when it scans the cache files it matches the root user and then
depending on the timestamp it can grab the wrong file.
Doug
[-- Attachment #2: nfs-utils-ignore-machine-cred.diff --]
[-- Type: text/plain, Size: 978 bytes --]
commit 891bf46cd23dbbb24188456aad29ac0ead2bc31f
Author: Doug Nazar <nazard.michi@gmail.com>
Date: Sat Jul 3 23:12:27 2010 -0400
When not using machine credentials for root, if the machine
credential cache file is newer than the root credential file
the wrong file will get picked. Ignore the machine file in this
case.
diff --git a/utils/gssd/krb5_util.c b/utils/gssd/krb5_util.c
index dccbeb6..d23654f 100644
--- a/utils/gssd/krb5_util.c
+++ b/utils/gssd/krb5_util.c
@@ -224,6 +224,13 @@ gssd_find_existing_krb5_ccache(uid_t uid, char *dirname, struct dirent **d)
free(namelist[i]);
continue;
}
+ if (uid == 0 && !root_uses_machine_creds &&
+ strstr(namelist[i]->d_name, "_machine_")) {
+ printerr(3, "CC file '%s' not available to root\n",
+ statname);
+ free(namelist[i]);
+ continue;
+ }
if (!query_krb5_ccache(buf, &princname, &realm)) {
printerr(3, "CC file '%s' is expired or corrupt\n",
statname);
next reply other threads:[~2010-07-04 3:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-04 3:30 Doug Nazar [this message]
2010-07-19 15:10 ` gssd picking wrong creds 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=4C300049.7040603@gmail.com \
--to=nazard.michi@gmail.com \
--cc=linux-nfs@vger.kernel.org \
/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).