Lines Matching refs:description

43 	- A description (for matching a key in a search).
67 (*) Each key has a description. This should be a printable string. The key
68 type provides an operation to perform a match between the description on a
136 A key of this type has a description and a payload that are arbitrary
146 The description can be arbitrary, but must be prefixed with a non-zero
148 separated from the rest of the description by a ':'. "logon" keys can
185 amount of description and payload space that can be consumed.
221 type and description.
295 file, giving information about their type, description and permissions.
394 (*) Create a new key of given type, description and payload and add it to the
401 If a key of the same type and description as that proposed already exists
409 description, and to instantiate it with the supplied payload and attach it
413 If the key type supports it, if the description is NULL or an empty
414 string, the key type will try and generate a description from the content
422 as the description (or NULL) and setting the payload to NULL.
425 recommended that a user defined key's description by prefixed with a type
438 key_serial_t request_key(const char *type, const char *description,
552 <type>;<uid>;<gid>;<perm>;<description>
554 Where type and description are strings, uid and gid are decimal, and perm
591 type and description will be discarded from the keyring as the new one is
610 const char *type, const char *description,
614 is found that matches the type and description criteria. Each keyring is
885 const char *description,
888 This is used to request a key or keyring with a description that matches
889 the description specified according to the key type's match_preparse()
907 const char *description,
920 const char *description,
927 const char *description,
986 const char *description)
999 struct key *keyring_alloc(const char *description, uid_t uid, gid_t gid,
1138 (*) int (*vet_description)(const char *description);
1140 This optional method is called to vet a key description. If the key type
1141 doesn't approve of the key description, it may return an error, otherwise
1152 char *description;
1165 If a description can be proposed from the payload contents, that should be
1166 attached as a string to the description field. This will be used for the
1167 key description if the caller of add_key() passes NULL or "".
1180 otherwise it is unused. It cleans up anything attached to the description
1250 to the default matcher function (which does an exact description match
1256 description to narrow down the search to a small number of keys.
1260 search that's not doing a simple direct match on the key description.
1277 exactly by their description.
1311 summarise a key's description and payload in text form.
1318 The description will not change, though the key's state may.