From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jim Rees <rees@umich.edu>
Cc: Sachin Prabhu <sprabhu@redhat.com>,
linux-nfs <linux-nfs@vger.kernel.org>,
Steve Dickson <steved@redhat.com>
Subject: Re: svcgssd: Allow administrators to specify timeout for the cached context
Date: Tue, 17 Jan 2012 13:49:01 -0500 [thread overview]
Message-ID: <20120117184901.GC15460@fieldses.org> (raw)
In-Reply-To: <20120117172444.GA3787@umich.edu>
On Tue, Jan 17, 2012 at 12:24:44PM -0500, Jim Rees wrote:
> J. Bruce Fields wrote:
>
> On Tue, Jan 17, 2012 at 11:31:33AM -0500, Jim Rees wrote:
> > Sachin Prabhu wrote:
> >
> > On Tue, 2012-01-17 at 08:49 -0500, Jim Rees wrote:
> > > Sachin Prabhu wrote:
> > >
> > > We had a user report that for an export shared with sec=krb5*, any
> > > changes in user credentials(ex: add user to a secondary group) take some
> > > time before they take effect over the NFS share.
> > >
> > > Re-authenticating, either by removing the service ticket or by re-running
> > > kinit at the client, should also flush the old credentials. Can you confirm
> > > that works?
> >
> > We have tried it but it doesn't work unless you actually clean up the
> > cache on the NFS server with the command
> > echo `date +'%s'` > /proc/net/rpc/auth.rpcsec.context/flush
> >
> > Bruce, shouldn't this work? Is this a bug or a feature?
>
> kdestroy, kinit, etc. on the client only affect userspace; the NFS
> client in the kernel continues to use the same gss context.
>
> I would find it surprising if kdestroy didn't actually discard my
> credentials. In fact I might even view this as a security risk.
Volunteers to fix this are welcomed.... I think this might be part of
the project Simo Sorce is working on, but I'm not sure.
--b.
next prev parent reply other threads:[~2012-01-17 18:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 11:44 svcgssd: Allow administrators to specify timeout for the cached context Sachin Prabhu
2012-01-17 13:49 ` Jim Rees
2012-01-17 15:38 ` Sachin Prabhu
2012-01-17 16:28 ` J. Bruce Fields
2012-01-17 16:31 ` Jim Rees
2012-01-17 16:34 ` J. Bruce Fields
2012-01-17 17:24 ` Jim Rees
2012-01-17 18:49 ` J. Bruce Fields [this message]
2012-01-18 12:14 ` Sachin Prabhu
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=20120117184901.GC15460@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
--cc=sprabhu@redhat.com \
--cc=steved@redhat.com \
/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.