Home
last modified time | relevance | path

Searched refs:keyrings (Results 1 – 11 of 11) sorted by relevance

/linux/security/integrity/
H A DKconfig20 bool "Digital signature verification using multiple keyrings"
26 using multiple keyrings. It defines separate keyrings for each
28 Different keyrings improves search performance, but also allow
30 This is useful for evm and module keyrings, when keys are
47 bool "Require all keys on the integrity keyrings be signed"
53 .evm keyrings be signed by a key on the system trusted
/linux/Documentation/ABI/testing/
H A Dima_policy33 [appraise_algos=] [keyrings=]
64 keyrings:= list of keyrings
158 measure func=KEY_CHECK keyrings=.builtin_trusted_keys|.ima
/linux/Documentation/security/keys/
H A Dcore.rst26 tokens, keyrings, etc.. These are represented in the kernel by struct key.
140 * Each process subscribes to three keyrings: a thread-specific keyring, a
161 * Each user ID resident in the system holds two special keyrings: a user
172 limits the total number of keys and keyrings, the other limits the total
179 Process-specific and thread-specific keyrings are not counted towards a
186 manipulate keys and keyrings.
192 userspace to request a key that can't be found in a process's keyrings.
222 This permits keyrings to be searched and keys to be found. Searches can
223 only recurse into nested keyrings that have search permission set.
257 The default keyrings associated with users will be labeled with the default
[all …]
H A Drequest-key.rst81 2) request_key() searches the process's subscribed keyrings to see if there's
107 This will permit it to then search the keyrings of process A with the
127 This is because process A's keyrings can't simply be attached to
/linux/security/integrity/ima/
H A Dima_policy.c127 struct ima_rule_opt_list *keyrings; /* Measure keys added to these keyrings */ member
412 ima_free_rule_opt_list(entry->keyrings); in ima_free_rule()
539 if (!rule->keyrings) in ima_match_rule_data()
542 opt_list = rule->keyrings; in ima_match_rule_data()
1650 entry->keyrings) { in ima_parse_rule()
1655 entry->keyrings = ima_alloc_rule_opt_list(args); in ima_parse_rule()
1656 if (IS_ERR(entry->keyrings)) { in ima_parse_rule()
1657 result = PTR_ERR(entry->keyrings); in ima_parse_rule()
1658 entry->keyrings = NULL; in ima_parse_rule()
2201 ima_show_rule_opt_list(m, entry->keyrings); in ima_policy_show()
H A DKconfig258 Keys may be added to the IMA or IMA blacklist keyrings, if the
260 machine (if configured), or secondary trusted keyrings. The
266 built-in, machine (if configured) or secondary trusted keyrings.
269 bool "Create IMA machine owner blacklist keyrings (EXPERIMENTAL)"
/linux/Documentation/bpf/
H A Dsigning.rst265 /* Serials of user keys/keyrings we additionally trust. */
394 and ``VERIFY_USE_PLATFORM_KEYRING`` select the corresponding system keyrings;
406 keyrings, or ``_USER`` for a user/session keyring. It is
415 serial. The system keyrings are trusted as a whole and expose no serial
/linux/Documentation/crypto/
H A Dasymmetric-keys.rst348 2) Restrict using the kernel builtin and secondary trusted keyrings
353 The kernel builtin and secondary trusted keyrings will be searched for the
/linux/Documentation/core-api/
H A Dwatch_queue.rst235 Notifications of this type indicate changes to keys and keyrings, including
/linux/Documentation/admin-guide/LSM/
H A Dipe.rst239 ``SYSTEM_TRUSTED_KEYRING``, or to the secondary and/or platform keyrings if
/linux/
H A DMAINTAINERS4160 L: keyrings@vger.kernel.org
6050 L: keyrings@vger.kernel.org
14451 L: keyrings@vger.kernel.org
14462 L: keyrings@vger.kernel.org
14473 L: keyrings@vger.kernel.org
14482 L: keyrings@vger.kernel.org
14491 L: keyrings@vger.kernel.org
14499 L: keyrings@vger.kernel.org
14507 L: keyrings@vger.kernel.org
14521 L: keyrings@vger.kernel.org