Searched refs:keyrings (Results 1 – 12 of 12) sorted by relevance
| /linux/security/integrity/ |
| H A D | Kconfig | 20 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 D | ima_policy | 33 [appraise_algos=] [keyrings=] 64 keyrings:= list of keyrings 158 measure func=KEY_CHECK keyrings=.builtin_trusted_keys|.ima
|
| /linux/Documentation/security/keys/ |
| H A D | core.rst | 26 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 D | request-key.rst | 81 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 D | ima_policy.c | 127 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() 1154 {Opt_keyrings, "keyrings=%s"}, 1647 ima_log_string(ab, "keyrings", args[0].from); in ima_parse_rule() 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() [all...] |
| H A D | Kconfig | 258 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 D | signing.rst | 265 * Serials of caller-supplied keyrings we are willing to stage. Empty 512 log message, whether or not provisioning ever completed. The system keyrings 521 Caller-supplied keyrings are for staging 534 keyrings; it should allowlist the specific serials it is willing to stage and 546 keyrings, ``_BPF`` for the bpf keyring, or ``_USER`` for a caller-supplied 556 serial. The system keyrings and the bpf keyring are trusted as a whole and 653 * carries no trust of its own. See "Caller-supplied keyrings are for
|
| /linux/Documentation/crypto/ |
| H A D | asymmetric-keys.rst | 348 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 D | watch_queue.rst | 235 Notifications of this type indicate changes to keys and keyrings, including
|
| /linux/Documentation/filesystems/ |
| H A D | fscrypt.rst | 892 added is limited by the user's quota for the keyrings service (see 984 Nevertheless, to add a key to one of the process-subscribed keyrings, 1023 process-subscribed keyrings mechanism. 1196 process-subscribed keyrings.
|
| /linux/Documentation/admin-guide/LSM/ |
| H A D | ipe.rst | 239 ``SYSTEM_TRUSTED_KEYRING``, or to the secondary and/or platform keyrings if
|
| /linux/ |
| H A D | MAINTAINERS | 4179 L: keyrings@vger.kernel.org 6085 L: keyrings@vger.kernel.org 14558 L: keyrings@vger.kernel.org 14569 L: keyrings@vger.kernel.org 14580 L: keyrings@vger.kernel.org 14589 L: keyrings@vger.kernel.org 14598 L: keyrings@vger.kernel.org 14606 L: keyrings@vger.kernel.org 14614 L: keyrings@vger.kernel.org 14628 L: keyrings [all...] |