From: Steve Dickson <SteveD@redhat.com>
To: David Howells <dhowells@redhat.com>
Cc: Benjamin Coddington <bcodding@uvm.edu>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsidmap: use multiple child keyrings
Date: Tue, 25 Mar 2014 06:41:16 -0400 [thread overview]
Message-ID: <53315D4C.9000407@RedHat.com> (raw)
In-Reply-To: <21458.1395739746@warthog.procyon.org.uk>
On 03/25/2014 05:29 AM, David Howells wrote:
> Steve Dickson <SteveD@redhat.com> wrote:
>
>> The reason the default is "id_resolver" is because the
>> is the name of the key ring defined in id_resolver.conf
>> is id_resolver. Now how that is translated into ".id_resolver"
>> in /proc/keys is not clear....
>
> Where in /etc/request-key.d/id_resolver.conf does it mention the name of a
> keyring?
>
> create id_resolver * * /usr/sbin/nfsidmap %k %d
I though "id_resolver" was the name.
>
> Match it against this line from request-key.conf:
>
> #OP TYPE DESCRIPTION CALLOUT INFO PROGRAM ARG1 ARG2 ARG3 ...
I should probably document this in request-key.conf.
>
> The "id_resolver" here is the name of the *key type* to be matched for that
> line. There is nothing here to do with keyrings.
Thanks for the clarification...
steved.
>
> David
>
next prev parent reply other threads:[~2014-03-25 10:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 21:08 [PATCH] nfsidmap: use multiple child keyrings Benjamin Coddington
2014-03-24 17:00 ` Steve Dickson
2014-03-24 18:00 ` Benjamin Coddington
2014-03-24 19:51 ` Steve Dickson
2014-03-24 21:03 ` Benjamin Coddington
2014-03-24 21:22 ` Steve Dickson
2014-03-24 22:10 ` Anna Schumaker
2014-03-24 23:57 ` Steve Dickson
2014-03-25 0:15 ` Benjamin Coddington
2014-03-25 9:35 ` David Howells
2014-03-25 12:49 ` Benjamin Coddington
2014-03-25 9:29 ` David Howells
2014-03-25 10:41 ` Steve Dickson [this message]
2014-03-25 9:34 ` David Howells
2014-03-25 12:56 ` Benjamin Coddington
2014-03-25 13:30 ` David Howells
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=53315D4C.9000407@RedHat.com \
--to=steved@redhat.com \
--cc=bcodding@uvm.edu \
--cc=dhowells@redhat.com \
--cc=linux-nfs@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 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.