Lines Matching +full:keys +full:- +full:per +full:- +full:group

6 Documentation/security/keys/core.rst).  This document explains more fully how
45 The main difference between the access points is that the in-kernel interface
50 The request_key_tag() call is like the in-kernel request_key(), except that it
51 also takes a domain tag that allows keys to be separated by namespace and
52 killed off as a group.
57 mechanism rather than using /sbin/request-key.
60 doesn't check for keys that are under construction and doesn't attempt to
61 construct missing keys.
70 forking and execution of /sbin/request-key.
95   4) request_key() then forks and executes /sbin/request-key with a new session
98   5) /sbin/request-key assumes the authority associated with key U.
100   6) /sbin/request-key execs an appropriate program to perform the actual
122 be created uninstantiated, another auth key (X) would be created (as per step
123 3) and another copy of /sbin/request-key spawned (as per step 4); but the
128 /sbin/request-key at the appropriate places because (a) execve will discard two
137 This is a short duration placeholder that causes any attempt at re-requesting
141 This is provided to prevent excessive repeated spawning of /sbin/request-key
144 Should the /sbin/request-key process exit anything other than 0 or die on a
158   2) It considers all the non-keyring keys within that keyring and, if any key
164   3) It then considers all the keyring-type keys in the keyring it's currently
173 When request_key() is invoked, if CONFIG_KEYS_REQUEST_CACHE=y, a per-task
174 one-key cache is first checked for a match.
196 per-task cache, displacing the previous key.  The cache is cleared on exit or