Re: [PATCH] nfsidmap: use multiple child keyrings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 03/25/2014 05:29 AM, David Howells wrote:
> Steve Dickson <SteveD@xxxxxxxxxx> 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
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux