All of lore.kernel.org
 help / color / mirror / Atom feed
From: christopher barry <Christopher.Barry@qlogic.com>
To: autofs@linux.kernel.org
Subject: Re: sudo and autofs
Date: Tue, 01 Apr 2008 16:27:29 -0400	[thread overview]
Message-ID: <1207081649.5226.29.camel@localhost> (raw)
In-Reply-To: <Pine.GSO.4.55.0803251247380.15841@loogie.intranet.csupomona.edu>

On Tue, 2008-03-25 at 12:51 -0800, Paul B. Henson wrote:
> On Mon, 24 Mar 2008, Jim Carter wrote:
> 
> > There are complaints that rpc.gssd only looks for /tmp/krb5cc_${UID}
> > whereas pam_krb5 uses /tmp/krb5cc__{UID}_XXXXXX (randomized by mktemp).
> > There is supposed to be a patch for this but I haven't discovered yet
> > whether I have it.
> 
> Even Red Hat 4 appears to have an rpc.gssd that does a more extensive
> search for credentials, presumably any reasonably modern distribution will
> as well.
> 
> > Access will not happen unless the KDC has nfs/${fqdn}@REALM for both hosts
> > (can't mount) and for the user (can't create security context for
> > read/write).
> 
> With newer versions of rpc.gssd you can tell it to use supplied credentials
> rather than machine credentials for the mount and for root access. This
> allows you to use secure NFS from a client on which you cannot obtain a
> host principal. It's not particularly convenient though...

Are both of you implying that with kerberized nfs, the local root user
can access a regular users nfs automounted home mounted with
-oroot_squash? Eg. Is this the answer I was looking for at the top of
this thread?

Regards,
-C

      reply	other threads:[~2008-04-01 20:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24  4:53 sudo and autofs chris barry
2008-03-21 10:45 ` Guillaume Rousse
2008-03-21 15:47   ` Jim Carter
2008-03-24 21:52     ` Paul B. Henson
2008-03-25  6:12       ` Jim Carter
2008-03-25 20:51         ` Paul B. Henson
2008-04-01 20:27           ` christopher barry [this message]

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=1207081649.5226.29.camel@localhost \
    --to=christopher.barry@qlogic.com \
    --cc=autofs@linux.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 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.