Home
last modified time | relevance | path

Searched refs:trusted (Results 1 – 25 of 145) sorted by relevance

123456

/linux-6.12.1/security/keys/trusted-keys/
DMakefile6 obj-$(CONFIG_TRUSTED_KEYS) += trusted.o
7 trusted-y += trusted_core.o
8 trusted-$(CONFIG_TRUSTED_KEYS_TPM) += trusted_tpm1.o
11 trusted-$(CONFIG_TRUSTED_KEYS_TPM) += trusted_tpm2.o
12 trusted-$(CONFIG_TRUSTED_KEYS_TPM) += tpm2key.asn1.o
14 trusted-$(CONFIG_TRUSTED_KEYS_TEE) += trusted_tee.o
16 trusted-$(CONFIG_TRUSTED_KEYS_CAAM) += trusted_caam.o
18 trusted-$(CONFIG_TRUSTED_KEYS_DCP) += trusted_dcp.o
DKconfig5 bool "TPM-based trusted keys"
17 Enable use of the Trusted Platform Module (TPM) as trusted key
24 bool "TEE-based trusted keys"
29 Enable use of the Trusted Execution Environment (TEE) as trusted
33 bool "CAAM-based trusted keys"
40 (CAAM) as trusted key backend.
43 bool "DCP-based trusted keys"
48 Enable use of NXP's DCP (Data Co-Processor) as trusted key backend.
/linux-6.12.1/crypto/asymmetric_keys/
Drestrict.c209 struct key *trusted, bool check_dest) in key_or_keyring_common() argument
222 if (!trusted && !check_dest) in key_or_keyring_common()
234 if (trusted) { in key_or_keyring_common()
235 if (trusted->type == &key_type_keyring) { in key_or_keyring_common()
237 key = find_asymmetric_key(trusted, sig->auth_ids[0], in key_or_keyring_common()
242 } else if (trusted->type == &key_type_asymmetric) { in key_or_keyring_common()
246 asymmetric_key_ids(trusted)->id; in key_or_keyring_common()
270 key = __key_get(trusted); in key_or_keyring_common()
277 key = __key_get(trusted); in key_or_keyring_common()
283 key = __key_get(trusted); in key_or_keyring_common()
[all …]
/linux-6.12.1/drivers/md/
Ddm-verity-loadpin.c21 bool trusted = false; in is_trusted_verity_target() local
39 trusted = true; in is_trusted_verity_target()
46 return trusted; in is_trusted_verity_target()
59 bool trusted = false; in dm_verity_loadpin_is_bdev_trusted() local
79 trusted = true; in dm_verity_loadpin_is_bdev_trusted()
85 return trusted; in dm_verity_loadpin_is_bdev_trusted()
/linux-6.12.1/Documentation/security/keys/
Dtrusted-encrypted.rst163 Users may override this by specifying ``trusted.rng=kernel`` on the kernel
172 using a specified ‘master’ key. The ‘master’ key can either be a trusted-key or
174 rooted in a trusted key, they are only as secure as the user key encrypting
185 TPM 1.2: By default, trusted keys are sealed under the SRK, which has the
207 keyctl add trusted name "new keylen [options]" ring
208 keyctl add trusted name "load hex_blob [pcrlock=pcrnum]" ring
244 keyctl add trusted name "new keylen" ring
245 keyctl add trusted name "load hex_blob" ring
257 keyctl add trusted name "new keylen" ring
258 keyctl add trusted name "load hex_blob" ring
[all …]
Dindex.rst11 trusted-encrypted
Decryptfs.rst35 time after the unsealing of a 'trusted' key in order to perform the mount in a
49 key-type:= 'trusted' | 'user'
/linux-6.12.1/certs/
DKconfig45 bool "Provide system-wide ring of trusted keys"
50 Provide a system keyring to which trusted keys can be added. Keys in
51 the keyring are considered to be trusted. Keys may be added at will
63 containing trusted X.509 certificates to be included in the default
65 also trusted.
76 image. This allows introducing a trusted certificate to the default
94 secondary trusted keyring.
97 bool "Only allow additional certs signed by keys on the builtin trusted keyring"
100 If set, only certificates signed by keys on the builtin trusted
101 keyring may be loaded onto the secondary trusted keyring.
[all …]
/linux-6.12.1/security/loadpin/
DKconfig31 digests it considers trusted. A verity backed filesystem is
32 considered trusted if its root digest is found in the list
33 of trusted digests.
35 The list of trusted verity can be populated through an ioctl
/linux-6.12.1/security/integrity/ima/
DKconfig198 be signed and verified by a public key on the trusted IMA
211 and verified by a public key on the trusted IMA keyring.
223 and verified by a key on the trusted IMA keyring.
256 machine (if configured), or secondary trusted keyrings. The
262 built-in, machine (if configured) or secondary trusted keyrings.
276 bool "Load X509 certificate onto the '.ima' trusted keyring"
281 loaded on the .ima trusted keyring. These public keys are
282 X509 certificates signed by a trusted key on the
284 loading from the kernel onto the '.ima' trusted keyring.
316 trusted boot based on IMA runtime policies.
/linux-6.12.1/Documentation/tee/
Dts-tee.rst59 [1] https://www.trustedfirmware.org/projects/trusted-services/
67 [5] https://trusted-services.readthedocs.io/en/v1.0.0/developer/service-access-protocols.html#abi
69 [6] https://git.trustedfirmware.org/TS/trusted-services.git/tree/components/rpc/ts_rpc/caller/linux…
71 [7] https://git.trustedfirmware.org/TS/trusted-services.git/tree/deployments/libts/arm-linux/CMakeL…
Dtee.rst12 A TEE is a trusted OS running in some secure environment, for example,
/linux-6.12.1/Documentation/admin-guide/hw-vuln/
Dcore-scheduling.rst21 user-designated trusted group can share a core. This increase in core sharing
101 trusted (same cookie) at any point in time. Kernel threads are assumed trusted.
110 the idle task is selected. Idle task is globally trusted.
126 priority task is not trusted with respect to the core wide highest priority
127 task. If a sibling does not have a trusted task to run, it will be forced idle
157 and are considered system-wide trusted. The forced-idling of siblings running
166 Core scheduling tries to guarantee that only trusted tasks run concurrently on a
168 concurrently or kernel could be running concurrently with a task not trusted by
173 Core scheduling selects only trusted tasks to run together. IPI is used to notify
207 allowing system processes (trusted tasks) to share a core.
/linux-6.12.1/include/crypto/
Dpublic_key.h70 struct key *trusted);
75 struct key *trusted);
/linux-6.12.1/security/integrity/evm/
DKconfig60 bool "Load an X509 certificate onto the '.evm' trusted keyring"
64 Load an X509 certificate onto the '.evm' trusted keyring.
67 onto the '.evm' trusted keyring. A public key can be used to
/linux-6.12.1/Documentation/ABI/testing/
Devm13 trusted/encrypted key stored in the Kernel Key
89 as part of the trusted boot. For more information on
90 creating and loading existing trusted/encrypted keys,
92 Documentation/security/keys/trusted-encrypted.rst. Both
Dsysfs-class-bdi71 be trusted to play fair.
84 which cannot be trusted to play fair.
112 trusted to play fair, or a nbd device.
/linux-6.12.1/security/integrity/
DKconfig52 .evm keyrings be signed by a key on the system trusted
56 bool "Provide keyring for platform/firmware trusted keys"
60 Provide a separate, distinct keyring for platform trusted keys, which
75 be trusted within the kernel.
/linux-6.12.1/Documentation/filesystems/
Doverlayfs.rst103 creation of trusted.* and/or user.* extended attributes, and must provide
149 as a zero-size regular file with the xattr "trusted.overlay.whiteout".
155 A directory is made opaque by setting the xattr "trusted.overlay.opaque"
161 "trusted.overlay.whiteout", should be additionally marked by setting the xattr
162 "trusted.overlay.opaque" to "x" on the merge directory itself.
163 This is needed to avoid the overhead of checking the "trusted.overlay.whiteout"
211 copied up (but not the contents). Then the "trusted.overlay.redirect"
251 upper directory is stored in a "trusted.overlay.upper" extended attribute
371 "trusted.overlayfs.metacopy" xattr which indicates that the upper file
374 the "trusted.overlayfs.metacopy" xattr is removed from the upper file.
[all …]
/linux-6.12.1/drivers/net/ethernet/intel/ice/
Dice_sriov.h47 int ice_set_vf_trust(struct net_device *netdev, int vf_id, bool trusted);
108 int __always_unused vf_id, bool __always_unused trusted) in ice_set_vf_trust() argument
Dice_sriov.c1411 ivi->trusted = vf->trusted; in ice_get_vf_cfg()
1512 int ice_set_vf_trust(struct net_device *netdev, int vf_id, bool trusted) in ice_set_vf_trust() argument
1532 if (trusted == vf->trusted) { in ice_set_vf_trust()
1539 vf->trusted = trusted; in ice_set_vf_trust()
1542 vf_id, trusted ? "" : "un"); in ice_set_vf_trust()
/linux-6.12.1/Documentation/admin-guide/device-mapper/
Dverity.rst64 and the salt. This hash should be trusted as there is no other authenticity
138 trusted keyring by default, or the secondary trusted keyring if
140 trusted keyring includes by default the builtin trusted keyring, and it can
142 already in the secondary trusted keyring.
/linux-6.12.1/include/linux/
Dif_link.h30 __u32 trusted; member
/linux-6.12.1/security/keys/
DMakefile31 obj-$(CONFIG_TRUSTED_KEYS) += trusted-keys/
/linux-6.12.1/drivers/net/ethernet/intel/ixgbe/
Dixgbe_sriov.c110 adapter->vfinfo[i].trusted = false; in __ixgbe_enable_sriov()
956 if (adapter->vfinfo[vf].pf_set_mac && !adapter->vfinfo[vf].trusted && in ixgbe_set_vf_mac_addr()
997 if (adapter->vfinfo[vf].pf_set_mac && !adapter->vfinfo[vf].trusted && in ixgbe_set_vf_macvlan_msg()
1178 !adapter->vfinfo[vf].trusted) { in ixgbe_update_vf_xcast_mode()
1821 if (adapter->vfinfo[vf].trusted == setting) in ixgbe_ndo_set_vf_trust()
1824 adapter->vfinfo[vf].trusted = setting; in ixgbe_ndo_set_vf_trust()
1849 ivi->trusted = adapter->vfinfo[vf].trusted; in ixgbe_ndo_get_vf_config()

123456