All of lore.kernel.org
 help / color / mirror / Atom feed
From: steve <steve-dZ4O0aZtNmBWk0Htik3J/w@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: kerberised cifs must have root krb5cc_0 cache?
Date: Sat, 13 Apr 2013 16:27:46 +0200	[thread overview]
Message-ID: <51696B62.7060103@steve-ss.com> (raw)

Ubuntu 12.10 clients in a Samba4 domain.

Hi
We are automounting cifs using:
-osec=krb5,multiuser.

It seems that unless the root cache:
/tmp/krb5cc_0
is present, users cannot enter the share even if they have a ticket with 
their own cache under /tmp

Is this the correct behavior?

If so, how to go about maintaining the cache alive. I thought about 
creating s domain user, say autofs-user and extracting his keytab. I 
would then run a script as root that calls k5start to maintain the 
ticket cache. But then, it could be overwritten if, say, Administrator 
logs in from a root account. Would that matter? So long as the root 
cache is present, does it matter which principal it has?

Cheers,
Steve

             reply	other threads:[~2013-04-13 14:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13 14:27 steve [this message]
     [not found] ` <51696B62.7060103-dZ4O0aZtNmBWk0Htik3J/w@public.gmane.org>
2013-04-14 12:05   ` kerberised cifs must have root krb5cc_0 cache? Jeff Layton
     [not found]     ` <20130414080525.4871cca2-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2013-04-14 12:44       ` Robert J. Hendelman Jr
     [not found]         ` <1933147666.1014.1365943484239.JavaMail.root-LqVPM+lxSZAcWVvVuXF20w@public.gmane.org>
2013-04-14 23:28           ` steve

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=51696B62.7060103@steve-ss.com \
    --to=steve-dz4o0aztnmbwk0htik3j/w@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 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.