From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: David Howells <dhowells@redhat.com>
Cc: jmorris@redhat.com, keyrings@linux-nfs.org,
linux-security-module@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KEYS: Allow special keyrings to be cleared
Date: Fri, 11 Nov 2011 17:41:57 -0500 [thread overview]
Message-ID: <1321051317.4810.17.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20111111160753.5190.36069.stgit@warthog.procyon.org.uk>
On Fri, 2011-11-11 at 16:07 +0000, David Howells wrote:
> The kernel contains some special internal keyrings, for instance the DNS
> resolver keyring :
>
> 2a93faf1 I----- 1 perm 1f030000 0 0 keyring .dns_resolver: empty
>
> It would occasionally be useful to allow the contents of such keyrings to be
> flushed by root (cache invalidation).
>
> Allow a flag to be set on a keyring to mark that someone possessing the
> sysadmin capability can clear the keyring, even without normal write access to
> the keyring.
>
> Set this flag on the special keyrings created by the DNS resolver, the NFS
> identity mapper and the CIFS identity mapper.
>
> Signed-off-by: David Howells <dhowells@redhat.com>
> Acked-by: Jeff Layton <jlayton@redhat.com>
> Acked-by: Steve Dickson <steved@redhat.com>
Acked-by: Trond Myklebust <Trond.Myklebust@netapp.com>
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2011-11-11 22:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 16:07 David Howells
2011-11-11 22:41 ` Trond Myklebust [this message]
2011-11-18 14:36 ` [Keyrings] " Steve Dickson
2011-11-18 18:33 ` Trond Myklebust
2012-01-18 15:28 David Howells
2012-01-18 15:31 David Howells
2012-01-19 4:03 ` James Morris
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=1321051317.4810.17.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=dhowells@redhat.com \
--cc=jmorris@redhat.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®