Lines Matching refs:key

8 ways NFS could obtain this information: placing a call to /sbin/request-key
11 NFS will attempt to call /sbin/request-key first.  If this succeeds, the
12 result will be cached using the generic request-key cache.  This call should
13 only fail if /etc/request-key.conf is not configured for the id_resolver key
14 type, see the "Configuring" section below if you wish to use the request-key
17 If the call to /sbin/request-key fails (if /etc/request-key.conf is not
18 configured with the id_resolver key type), then the idmapper will ask the
26 The file /etc/request-key.conf will need to be modified so /sbin/request-key can
34 The last parameter, 600, defines how many seconds into the future the key will
38 id mapper uses for key descriptions:
46 would edit your request-key.conf so it look similar to this:
54 request-key will find the first matching line and corresponding program.  In
58 See <file:Documentation/security/keys-request-key.txt> for more information
59 about the request-key function.
65 nfs.idmap is designed to be called by request-key, and should not be run "by
66 hand".  This program takes two arguments, a serialized key and a key
67 description.  The serialized key is first converted into a key_serial_t, and
75 nfs.idmap will return 0 if the key was instantiated, and non-zero otherwise.