Searched full:keys (Results 1 – 25 of 174) sorted by relevance
1234567
| /Documentation/security/keys/ |
| D | trusted-encrypted.rst | 2 Trusted and Encrypted Keys
5 Trusted and Encrypted Keys are two new key types added to the existing kernel
6 key ring service. Both of these new types are variable length symmetric keys,
7 and in both cases all keys are created in the kernel, and user space sees,
8 stores, and loads only encrypted blobs. Trusted Keys require the availability
9 of a Trust Source for greater security, while Encrypted Keys can be used on any
17 A trust source provides the source of security for Trusted Keys. This
23 consumer of the Trusted Keys to determine if the trust source is sufficiently
49 DCP provides two keys that can be used as root of trust: the OTP key
78 Keys can be optionally sealed to specified PCR (integrity measurement)
[all …]
|
| D | core.rst | 5 This service allows cryptographic keys, authentication tokens, cross-domain
10 other keys. Processes each have three standard keyring subscriptions that a
11 kernel service can search for relevant keys.
25 In this context, keys represent units of cryptographic data, authentication
47 kernel by a kernel service (such as a filesystem) before keys of that type
53 Should a type be removed from the system, all the keys of that type will
65 instantiation function. Keys can also be immortal.
68 actual "key". In the case of a keyring, this is a list of keys to which
86 Keys being requested from userspace will be in this state.
96 * Expired. Keys can have lifetimes set. If their lifetime is exceeded,
[all …]
|
| /Documentation/devicetree/bindings/input/ |
| D | input-reset.txt | 3 A simple binding to represent a set of keys as described in
4 include/uapi/linux/input.h. This is to communicate a sequence of keys to the
5 sysrq driver. Upon holding the keys for a specified amount of time (if
8 Key sequences are global to the system but all the keys in a set must be coming
12 a set of keys.
18 timeout-ms: duration keys must be pressed together in milliseconds before
|
| D | mediatek,pmic-keys.yaml | 4 $id: http://devicetree.org/schemas/input/mediatek,pmic-keys.yaml#
7 title: MediaTek PMIC Keys
27 - mediatek,mt6323-keys
28 - mediatek,mt6331-keys
29 - mediatek,mt6357-keys
30 - mediatek,mt6358-keys
31 - mediatek,mt6397-keys
|
| D | gpio-keys.yaml | 4 $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
7 title: GPIO attached keys
15 - gpio-keys
16 - gpio-keys-polled
88 deasserted, or both. This property is only valid for keys that wake up the
141 const: gpio-keys-polled
155 gpio-keys {
156 compatible = "gpio-keys";
|
| D | adc-keys.yaml | 4 $id: http://devicetree.org/schemas/input/adc-keys.yaml#
17 const: adc-keys
27 Voltage above or equal to which all the keys are considered up.
79 adc-keys {
80 compatible = "adc-keys";
|
| D | iqs62x-keys.yaml | 4 $id: http://devicetree.org/schemas/input/iqs62x-keys.yaml#
7 title: Azoteq IQS620A/621/622/624/625 Keys and Switches
21 These functions are collectively represented by a "keys" child node from the
29 - azoteq,iqs620a-keys
30 - azoteq,iqs621-keys
31 - azoteq,iqs622-keys
32 - azoteq,iqs624-keys
33 - azoteq,iqs625-keys
120 - azoteq,iqs624-keys
121 - azoteq,iqs625-keys
|
| /Documentation/block/ |
| D | inline-encryption.rst | 19 keys directly in low-level I/O requests. However, most inline encryption
61 - Inline encryption hardware usually (but not always) requires that keys be
64 key for every I/O request, but rather keep track of which keys are in the
67 - Upper layers typically define a specific end-of-life for crypto keys, e.g.
69 At these times, keys are wiped from memory. We must provide a way for upper
70 layers to also evict keys from any keyslots they are present in.
98 functions to program and evict keys) to upper layers. Each device driver that
170 encryption hardware, the crypto API doesn't accept keys directly in requests but
171 rather requires that keys be set ahead of time, and setting keys can be
307 Hardware-wrapped keys
[all …]
|
| /Documentation/arch/arm64/ |
| D | pointer-authentication.rst | 36 The extension provides five separate keys to generate PACs - two for
46 exec*() time. The keys are shared by all threads within the process, and
61 In addition to exec(), keys can also be reinitialized to random values
64 specifies which keys are to be reinitialized; specifying 0 means "all
65 keys".
85 used to get and set the keys for a thread.
111 Enabling and disabling keys
115 PAC keys are enabled in a particular task. It takes two arguments, the
117 and PR_PAC_APDBKEY specifying which keys shall be affected by this prctl,
125 disables all keys except the IB key.
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | iqs62x.yaml | 40 keys:
41 $ref: /schemas/input/iqs62x-keys.yaml
72 keys {
73 compatible = "azoteq,iqs620a-keys";
119 keys {
120 compatible = "azoteq,iqs620a-keys";
156 keys {
157 compatible = "azoteq,iqs624-keys";
|
| D | mt6397.txt | 10 - Keys
59 - keys
61 - compatible: "mediatek,mt6323-keys"
62 - compatible: "mediatek,mt6331-keys"
63 - compatible: "mediatek,mt6397-keys"
64 see ../input/mtk-pmic-keys.txt
|
| D | mediatek,mt6357.yaml | 21 - Keys
78 keys:
80 $ref: /schemas/input/mediatek,pmic-keys.yaml
83 MT6357 power and home keys.
131 keys {
132 compatible = "mediatek,mt6357-keys";
|
| /Documentation/core-api/ |
| D | protection-keys.rst | 4 Memory Protection Keys
7 Memory Protection Keys provide a mechanism for enforcing page-based
20 a "protection key", giving 16 possible keys.
24 and Write Disable) for each of 16 keys.
38 giving 8 possible keys.
92 The kernel attempts to make protection keys consistent with the
98 you can expect the same effects with protection keys when doing this::
115 to SEGV_PKERR when violating protection keys versus SEGV_ACCERR when
|
| /Documentation/process/ |
| D | maintainer-pgp-guide.rst | 55 a secure working environment and safeguard the PGP keys used to
127 - **[S]** keys can be used for signing
128 - **[E]** keys can be used for encryption
129 - **[A]** keys can be used for authentication
130 - **[C]** keys can be used for certifying other keys
135 a physical "master key" can be used to open locks made for other keys).
154 can be used to indicate relationship with other keys. Only the **[C]**
157 - add or revoke other keys (subkeys) with S/E/A capabilities
160 - sign other people's keys for web of trust purposes
162 By default, GnuPG creates the following when generating new keys:
[all …]
|
| /Documentation/driver-api/nvdimm/ |
| D | security.rst | 45 The security keys are managed on the basis of a single key per DIMM. The
49 all the keys are in the kernel user keyring for unlock.
54 See file ``Documentation/security/keys/trusted-encrypted.rst`` for creating
55 encrypted-keys of enc32 format. TPM usage with a master trusted key is
56 preferred for sealing the encrypted-keys.
64 relevant encrypted-keys into the kernel user keyring during the initramfs phase.
65 This provides the unlock function access to all the related keys that contain
67 keys are injected before libnvdimm is loaded by modprobe.
85 The freeze operation does not require any keys. The security config can be
|
| /Documentation/crypto/ |
| D | asymmetric-keys.rst | 11 - Accessing asymmetric keys.
21 The "asymmetric" key type is designed to be a container for the keys used in
72 only keys of the specified subtype (e.g. tpm) will be matched. For
77 Looking in /proc/keys, the last 8 hex digits of the key fingerprint are
83 Accessing Asymmetric Keys
86 For general access to asymmetric keys from within the kernel, the following
91 This gives access to functions for dealing with asymmetric / public keys.
164 Asymmetric keys have a subtype that defines the set of operations that can be
174 #include <keys/asymmetric-subtype.h>
192 Asymmetric keys point to this with their payload[asym_subtype] member.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-input-cros-ec-keyb | 4 Description: A space separated list of scancodes for the top row keys,
5 ordered by the physical positions of the keys, from left
|
| D | evm | 16 asymmetric key. These keys are loaded onto root's
86 INTEGRITY_UNKNOWN. Loading keys and signaling EVM
90 creating and loading existing trusted/encrypted keys,
92 Documentation/security/keys/trusted-encrypted.rst. Both
94 core/ima-setup) have support for loading keys at boot
|
| D | sysfs-driver-hid-corsair | 6 where G-keys triggers their regular key codes. "HW" for
7 hardware playback mode where the G-keys play their macro
|
| /Documentation/userspace-api/media/rc/ |
| D | rc-tables.rst | 14 keys on IR.
46 - **Numeric keys**
411 - **Colored keys**
635 - **Navigation keys**
711 - **Miscellaneous keys**
730 It should be noted that, sometimes, there some fundamental missing keys
743 - On simpler IR's, without separate channel keys, you need to map UP
748 - On simpler IR's, without separate channel keys, you need to map
753 - On simpler IR's, without separate volume keys, you need to map
758 - On simpler IR's, without separate volume keys, you need to map
|
| /Documentation/admin-guide/ |
| D | module-signing.rst | 8 .. - Generating signing keys.
9 .. - Public keys in the kernel.
29 This facility uses X.509 ITU-T standard certificates to encode the public keys
101 ``certs/signing_key.pem`` will disable the autogeneration of signing keys
114 (5) :menuselection:`Additional X.509 keys for default system keyring`
126 Generating signing keys
184 Public keys in the kernel
187 The kernel contains a ring of public keys that can be viewed by root. They're
190 [root@deneb ~]# cat /proc/keys
200 Further, the architecture code may take public keys from a hardware store and
[all …]
|
| /Documentation/filesystems/ |
| D | fscrypt.rst | 27 with different keys and to have unencrypted files on the same
107 security vulnerability, can compromise all encryption keys that are
110 However, fscrypt allows encryption keys to be removed from the kernel,
117 thereby wiping their per-file keys and making them once again appear
122 - Per-file keys for in-use files will *not* be removed or wiped.
135 containing keys to prevent it from being swapped out.
144 - Secret keys might still exist in CPU registers or in other places
164 - Non-root users cannot securely remove encryption keys.
173 Master Keys
177 keys can be up to 64 bytes long, and must be at least as long as the
[all …]
|
| /Documentation/admin-guide/laptops/ |
| D | sonypi.rst | 22 - Fn keys
24 - programmable keys, back, help, zoom, thumbphrase buttons, etc.
88 programmable keys events). The default event mask is
112 keyboard reporting the pressing of the special keys.
132 Fn-keys which put the laptop in sleeping state, or switch the
134 driver disables all APM management for those keys, by enabling the
136 you have one of those laptops with working Fn keys and want to
|
| /Documentation/translations/zh_CN/core-api/ |
| D | protection-keys.rst | 4 :Original: Documentation/core-api/protection-keys.rst
14 .. _cn_core-api_protection-keys:
20 用户空间的内存保护密钥（Memory Protection Keys for Userspace，PKU，亦
|
| /Documentation/staging/ |
| D | static-keys.rst | 2 Static Keys
21 DEFINE_STATIC_KEY_ARRAY_TRUE(keys, count);
22 DEFINE_STATIC_KEY_ARRAY_FALSE(keys, count);
29 Static keys allows the inclusion of seldom used features in
65 kernel code paths should be able to make use of the static keys facility.
94 the basis for the static keys facility.
126 Keys defined via DEFINE_STATIC_KEY_TRUE(), or DEFINE_STATIC_KEY_FALSE, may
172 Where an array of keys is required, it can be defined as::
174 DEFINE_STATIC_KEY_ARRAY_TRUE(keys, count);
178 DEFINE_STATIC_KEY_ARRAY_FALSE(keys, count);
[all …]
|
1234567