/openbmc/linux/security/keys/trusted-keys/ |
H A D | Makefile | 6 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
|
H A D | Kconfig | 2 bool "TPM-based trusted keys" 13 Enable use of the Trusted Platform Module (TPM) as trusted key 20 bool "TEE-based trusted keys" 24 Enable use of the Trusted Execution Environment (TEE) as trusted 28 bool "CAAM-based trusted keys" 34 (CAAM) as trusted key backend.
|
/openbmc/linux/crypto/asymmetric_keys/ |
H A D | restrict.c | 205 struct key *trusted, bool check_dest) in key_or_keyring_common() argument 218 if (!trusted && !check_dest) in key_or_keyring_common() 230 if (trusted) { in key_or_keyring_common() 231 if (trusted->type == &key_type_keyring) { in key_or_keyring_common() 238 } else if (trusted->type == &key_type_asymmetric) { in key_or_keyring_common() 242 asymmetric_key_ids(trusted)->id; in key_or_keyring_common() 266 key = __key_get(trusted); in key_or_keyring_common() 273 key = __key_get(trusted); in key_or_keyring_common() 279 key = __key_get(trusted); in key_or_keyring_common() 327 struct key *trusted) in restrict_link_by_key_or_keyring() argument [all …]
|
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-a/ |
H A D | trusted-firmware-a_%.bbappend | 6 MACHINE_TFA_REQUIRE:corstone1000 = "trusted-firmware-a-corstone1000.inc" 7 MACHINE_TFA_REQUIRE:fvp-base = "trusted-firmware-a-fvp-base.inc" 8 MACHINE_TFA_REQUIRE:juno = "trusted-firmware-a-juno.inc" 9 MACHINE_TFA_REQUIRE:n1sdp = "trusted-firmware-a-n1sdp.inc" 10 MACHINE_TFA_REQUIRE:sgi575 = "trusted-firmware-a-sgi575.inc" 11 MACHINE_TFA_REQUIRE:tc = "trusted-firmware-a-tc.inc"
|
H A D | trusted-firmware-a_2.9.0.bb | 1 require recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
H A D | TrustedComponent.interface.yaml | 2 Interface to query trusted component info. 11 The type of trusted component, such as any physical distinction about 12 the trusted component. 19 object that the trusted component is reported by. 36 The type of trusted component, such as any physical distinction about 37 the trusted component. 41 A discrete trusted component. It is "discrete" when basic 46 An integrated trusted component.
|
/openbmc/linux/drivers/md/ |
H A D | dm-verity-loadpin.c | 21 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()
|
/openbmc/openbmc/meta-arm/documentation/ |
H A D | trusted-services.md | 4 in `meta-arm/recipes-security/trusted-services` 42 3. trusted-firmware-a might require platform specific TF-A build parameters (SPD and SPMC details o… 43 …See `meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend` for qemuarm64-securebo… 44 and in `meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-n1sdp.inc` and 45 …`meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-corstone1000.inc` for N1SDP and Co… 55 See `ci/trusted-services.yml` for an example how to include them into an image. 59 [^1]: https://trusted-services.readthedocs.io/en/integration/overview/index.html 61 [^2]: https://trusted-services.readthedocs.io/en/integration/deployments/secure-partitions.html 63 [^3]: https://trusted-services.readthedocs.io/en/integration/deployments/test-executables.html
|
/openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/trusted-firmware-m/ |
H A D | trusted-firmware-m_2.0.0.bb | 1 require recipes-bsp/trusted-firmware-m/trusted-firmware-m-${PV}-src.inc 2 require recipes-bsp/trusted-firmware-m/trusted-firmware-m.inc
|
H A D | trusted-firmware-m-scripts-native_2.0.0.bb | 1 require recipes-bsp/trusted-firmware-m/trusted-firmware-m-${PV}-src.inc 2 require recipes-bsp/trusted-firmware-m/trusted-firmware-m-scripts-native.inc
|
H A D | trusted-firmware-m-2.0.0-src.inc | 1 # Common src definitions for trusted-firmware-m and trusted-firmware-m-scripts 10 SRC_URI_TRUSTED_FIRMWARE_M ?= "git://git.trustedfirmware.org/TF-M/trusted-firmware-m.git;protocol=h…
|
/openbmc/linux/Documentation/devicetree/bindings/arm/firmware/ |
H A D | tlm,trusted-foundations.yaml | 4 $id: http://devicetree.org/schemas/arm/firmware/tlm,trusted-foundations.yaml# 18 const: trusted-foundations 21 const: tlm,trusted-foundations 41 trusted-foundations { 42 compatible = "tlm,trusted-foundations";
|
/openbmc/phosphor-fan-presence/docs/monitor/ |
H A D | class.md | 7 determines if the group is trusted by checking each fan sensors listed within 8 the trust group against an algorithm that returns whether they can be trusted or 14 - Determines if the group is trusted by checking if any sensors in the group 16 group are trusted and therefore monitoring of all the sensors in the group
|
/openbmc/linux/Documentation/security/keys/ |
H A D | trusted-encrypted.rst | 176 keyctl add trusted name "new keylen [options]" ring 213 keyctl add trusted name "new keylen" ring 214 keyctl add trusted name "load hex_blob" ring 226 keyctl add trusted name "new keylen" ring 227 keyctl add trusted name "load hex_blob" ring 253 key-type:= 'trusted' | 'user' 255 Examples of trusted and encrypted key usage 266 $ keyctl add trusted kmk "new 32" @u 287 Load a trusted key from the saved blob:: 289 $ keyctl add trusted kmk "load `cat kmk.blob`" @u [all …]
|
/openbmc/phosphor-fan-presence/monitor/ |
H A D | trust_manager.hpp | 86 auto trusted = true; in checkTrust() local 97 trusted = false; in checkTrust() 114 return trusted; in checkTrust()
|
/openbmc/u-boot/doc/ |
H A D | README.armada-secureboot | 1 The trusted boot framework on Marvell Armada 38x 6 1. Overview of the trusted boot 15 1. Overview of the trusted boot 18 The Armada's trusted boot framework enables the SoC to cryptographically verify 88 trusted boot (also known as "security header") 93 debugging of devices employing the trusted boot 204 trusted boot framework, several new options were added to faciliate 215 BOX_ID - The BoxID to be used for trusted debugging (a integer 219 JTAG_DELAY - The JTAG delay to be used for trusted debugging (a 223 in the image (that is, whether to use the trusted debug [all …]
|
/openbmc/linux/security/loadpin/ |
H A D | Kconfig | 28 digests it considers trusted. A verity backed filesystem is 29 considered trusted if its root digest is found in the list 30 of trusted digests. 32 The list of trusted verity can be populated through an ioctl
|
/openbmc/openbmc/meta-arm/meta-arm/recipes-security/trusted-services/ |
H A D | trusted-services-src.inc | 5 …git.trustedfirmware.org/TS/trusted-services.git;protocol=https;branch=integration;name=trusted-ser… 20 S = "${WORKDIR}/git/trusted-services" 63 SRCREV_FORMAT = "trusted-services_dtc_mbedtls_nanopb_qcbor_tcose_cpputest_libmetal_openamp"
|
H A D | ts-service-test_git.bb | 3 on an Arm platform with real deployments of trusted services." 7 require trusted-services.inc
|
H A D | trusted-services.inc | 2 HOMEPAGE = "https://trusted-services.readthedocs.io/en/latest/index.html" 12 require trusted-services-src.inc 14 # By default bitbake includes only ${S} (i.e git/trusted-services) in the maps.
|
H A D | ts-demo_git.bb | 3 on an Arm platform with real deployments of trusted services." 7 require trusted-services.inc
|
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/images/ |
H A D | tc-artifacts-image.bb | 13 # The last image to be built is trusted-firmware-a 14 DEPENDS += " trusted-firmware-a"
|
/openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/trusted-firmware-a/ |
H A D | trusted-firmware-a_2.10.3.bb | 1 require recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc
|
/openbmc/linux/certs/ |
H A D | Kconfig | 43 bool "Provide system-wide ring of trusted keys" 48 Provide a system keyring to which trusted keys can be added. Keys in 49 the keyring are considered to be trusted. Keys may be added at will 61 containing trusted X.509 certificates to be included in the default 63 also trusted. 74 image. This allows introducing a trusted certificate to the default 91 into the kernel or already in the secondary trusted keyring. 137 they are signed and vouched by a certificate from the builtin trusted
|
/openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/ |
H A D | musca-b1.md | 14 To build the trusted firmware-m: 15 ```bash$ bitbake trusted-firmware-m```
|