From: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
To: "Dey, John F" <jfdey-rEd9KcVInK8dYYaOPf09RA@public.gmane.org>
Cc: "jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
<jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: questions cifs.upcall.c
Date: Thu, 24 Mar 2016 11:24:27 -0400 [thread overview]
Message-ID: <20160324112427.46b0ad33@synchrony.poochiereds.net> (raw)
In-Reply-To: <B6CF10CD-10A5-4A30-93D8-E89FE6ED0697-q9hIisBwmLrYtjvyW6yDsg@public.gmane.org>
On Mon, 21 Mar 2016 17:37:35 +0000
"Dey, John F" <jfdey-rEd9KcVInK8dYYaOPf09RA@public.gmane.org> wrote:
> Jeff,
>
> I am setting krb5.conf default_ccache_name = (shared mount point). The MIT krb5 routines work fine with the shared drive, but cifs.upcall is not reading the /etc/krb5.conf file to find the new location. Default search locations seem to be hard-coded into cifs.upcall.
>
> I am using Ubuntu 14.04 cifs-utils 6.0. I have also check Ubuntu 16.04 with cifs-util 6.5.
>
> In 2009 you had a patch to read the krb5CCNAME environment variable, this patch has since been removed. Setting the default path in krb5.conf seems to solve a lot of problems but cifs.upcall is not checking that location. Is there a reason why the krb5.conf is not checked?
>
> WHY are we doing this? We run a large linux cluster. Users interact with a set of head nodes. When users login to the headnotes their krb5 ticket is updated. From head nodes users can run jobs on the Linux cluster. The cluster nodes do not have updated tickets so users jobs fail. So we would like to use a shared drive for the tickets so that all the cluster nodes have an updated ticket.
>
> Thanks
>
> John Dey
> Jidey-rEd9KcVInK8dYYaOPf09RA@public.gmane.org
> John-pGYbrA4uTiZBDgjK7y7TUQ@public.gmane.org
>
>
>
(cc'ing linux-cifs mailing list)
Hmm, it's been so long since I looked at that code, I've forgotten how
it works. Let's see...
ccdir = resolve_krb5_dir(CIFS_DEFAULT_KRB5_USER_DIR, uid);
if (ccdir != NULL)
find_krb5_cc(ccdir, uid, &best_cache, &best_time);
ccname = find_krb5_cc(CIFS_DEFAULT_KRB5_DIR, uid, &best_cache,
&best_time);
...and those CIFS_DEFAULT_* macros are:
#define CIFS_DEFAULT_KRB5_DIR "/tmp"
#define CIFS_DEFAULT_KRB5_USER_DIR "/run/user/%U"
So yeah, it does seem to be hardcoded. Why was it written that way?
ISTR that older versions of krb5 libs made it hard to get to that
variable from the config file, but maybe I'm remembering wrong.
It probably wouldn't be too hard to fix, but you'd have to dig into the
krb5 library API. I doubt I'll have time to do that anytime soon. If
you or your OS vendor wants to propose some patches however, I'd be
happy to review (and eventually) merge them.
Cheers,
--
Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
next parent reply other threads:[~2016-03-24 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B6CF10CD-10A5-4A30-93D8-E89FE6ED0697@fhcrc.org>
[not found] ` <B6CF10CD-10A5-4A30-93D8-E89FE6ED0697-q9hIisBwmLrYtjvyW6yDsg@public.gmane.org>
2016-03-24 15:24 ` Jeff Layton [this message]
[not found] ` <20160324112427.46b0ad33-08S845evdOaAjSkqwZiSMmfYqLom42DlXqFh9Ls21Oc@public.gmane.org>
2016-03-24 15:46 ` questions cifs.upcall.c Dey, John F
[not found] ` <E338E595-7E4A-4738-A69F-6235203605A0-q9hIisBwmLrYtjvyW6yDsg@public.gmane.org>
2016-03-24 16:50 ` Jeff Layton
[not found] ` <20160324125057.59d34f5b-08S845evdOaAjSkqwZiSMmfYqLom42DlXqFh9Ls21Oc@public.gmane.org>
2016-03-25 22:11 ` Dey, John F
[not found] ` <A8994554-2D81-4D87-A767-EF9408C1C86E-q9hIisBwmLrYtjvyW6yDsg@public.gmane.org>
2016-04-01 22:30 ` Jeff Layton
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=20160324112427.46b0ad33@synchrony.poochiereds.net \
--to=jlayton-eunubhrolfbytjvyw6ydsg@public.gmane.org \
--cc=jfdey-rEd9KcVInK8dYYaOPf09RA@public.gmane.org \
--cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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