All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nalin Dahyabhai <nalin-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Finding krb5 ccaches of new types in new locations
Date: Tue, 21 Aug 2012 18:54:43 -0400	[thread overview]
Message-ID: <20120821225443.GG9511@redhat.com> (raw)

One of the things we're currently trying to do for Fedora 18 is to move
user credential caches from being files ("FILE" ccaches) in /tmp to
being subdirectories ("DIR" ccaches) under /run/user/${UID}.  To be very
specific, we'd go from using one of:
  FILE:/tmp/krb5cc_${UID}
  FILE:/tmp/krb5cc_${UID}_XXXXXX
to possibly using one of those, and possibly also any of these:
  DIR:/run/user/${UID}/krb5cc
  DIR:/run/user/${UID}/krb5cc_XXXXXX
  FILE:/run/user/${UID}/krb5cc
  FILE:/run/user/${UID}/krb5cc_XXXXXX
  DIR:/tmp/krb5cc_${UID}
  DIR:/tmp/krb5cc_${UID}_XXXXXX

Some would be more likely than others, but my goal here is to make sure
that cifs.upcall can find credentials in these other locations.  I'll
reply to this with suggested patches.

Thanks,

Nalin

             reply	other threads:[~2012-08-21 22:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21 22:54 Nalin Dahyabhai [this message]
     [not found] ` <20120821225443.GG9511-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-08-21 22:56   ` [PATCH 1/2] also consider DIR:-type ccaches Nalin Dahyabhai
     [not found]     ` <20120821225624.GH9511-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-08-24 10:21       ` Jeff Layton
2012-08-21 22:56   ` [PATCH 2/2] scan /run/user/${UID} for ccaches, too Nalin Dahyabhai
     [not found]     ` <20120821225648.GI9511-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-08-24 10:21       ` Jeff Layton
2012-08-22 17:00   ` Finding krb5 ccaches of new types in new locations 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=20120821225443.GG9511@redhat.com \
    --to=nalin-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 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.