Home
last modified time | relevance | path

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

1234567891011

/openbmc/linux/security/keys/trusted-keys/
H A 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
H A DKconfig2 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 Drestrict.c205 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()
233 key = find_asymmetric_key(trusted, sig->auth_ids[0], 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()
[all …]
/openbmc/linux/drivers/md/
H A 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()
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-a/
H A Dtrusted-firmware-a_%.bbappend6 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:sbsa-ref = "trusted-firmware-a-sbsa-ref.inc"
10 MACHINE_TFA_REQUIRE:sgi575 = "trusted-firmware-a-sgi575.inc"
/openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/trusted-firmware-m/
H A Dtrusted-firmware-m_2.1.0.bb1 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 Dtrusted-firmware-m-scripts-native_2.1.0.bb1 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
/openbmc/openbmc/meta-arm/documentation/
H A Dtrusted-services.md4 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-corstone1000.inc` for theCo…
58 See `ci/trusted-services.yml` for an example how to include them into an image.
62 [^1]: https://trusted-services.readthedocs.io/en/integration/overview/index.html
64 [^2]: https://trusted-services.readthedocs.io/en/integration/deployments/secure-partitions.html
66 [^3]: https://trusted-services.readthedocs.io/en/integration/deployments/test-executables.html
H A Dquick-start.md44 If, as an example, we’re wanting to develop trusted-firmware-a; then fvp-base will work for us. 
55 …ware being used on the machine above (in the above example, this will be trusted-firmware-a for fv…
58 $ devtool modify trusted-firmware-a
61 …d print a path at the end where the source code was checked out.  In the trusted-firmware-a exampl…
63 > /builder/meta-arm/build/workspace/sources/trusted-firmware-a
70 $ devtool build trusted-firmware-a
88 $ mv 0001-example.patch ~/meta-arm/meta-arm/recipes-bsp/trusted-firmware-a/files/
90 $ devtool reset trusted-firmware-a
91 …:append = " file://0001-example.patch" >> meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware…
/openbmc/linux/Documentation/security/keys/
H A Dtrusted-encrypted.rst132 Users may override this by specifying ``trusted.rng=kernel`` on the kernel
141 using a specified ‘master’ key. The ‘master’ key can either be a trusted-key or
143 rooted in a trusted key, they are only as secure as the user key encrypting
154 TPM 1.2: By default, trusted keys are sealed under the SRK, which has the
176 keyctl add trusted name "new keylen [options]" ring
177 keyctl add trusted name "load hex_blob [pcrlock=pcrnum]" 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
[all …]
/openbmc/phosphor-fan-presence/docs/monitor/
H A Dclass.md7 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/u-boot/doc/
H A DREADME.armada-secureboot1 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
48 image, which employs this trusted boot framework, the following tasks need to
61 The documentation of the trusted boot mode is contained in part 1, chapter
88 trusted boot (also known as "security header")
92 Trusted debug mode - A special mode for the trusted boot that allows
93 debugging of devices employing the trusted boot
124 For the trusted boot framework, a additional header is added to the boot image.
[all …]
/openbmc/phosphor-fan-presence/monitor/
H A Dtrust_manager.hpp86 auto trusted = true; in checkTrust() local
97 trusted = false; in checkTrust()
114 return trusted; in checkTrust()
/openbmc/openbmc/meta-arm/meta-arm/recipes-security/trusted-services/
H A Dtrusted-services-src.inc5 …://git.trustedfirmware.org/TS/trusted-services.git;protocol=https;branch=main;name=trusted-service…
18 S = "${WORKDIR}/git/trusted-services"
51 SRCREV_FORMAT = "trusted-services_dtc_mbedtls_nanopb_qcbor_tcose_cpputest"
H A Dts-service-test_git.bb3 on an Arm platform with real deployments of trusted services."
7 require trusted-services.inc
H A Dtrusted-services.inc2 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.
/openbmc/linux/security/loadpin/
H A DKconfig28 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-bsp/documentation/corstone1000/
H A Dchange-log.rst41 | trusted-firmware-a | 2.11.0 |
43 | trusted-firmware-m | 2.1.0 |
112 | trusted-firmware-a | 2.10.4 |
114 | trusted-firmware-m | 2.0.0 |
183 | trusted-firmware-a | 2.9.0 |
185 | trusted-firmware-m | 1.8.1 |
253 | trusted-firmware-a | 2.8.0-r0 |
255 | trusted-firmware-m | 1.7.0-r0 |
319 | trusted-firmware-a | 2.7.0 |
321 | trusted-firmware-m | 1.6.0 |
/openbmc/linux/certs/
H A DKconfig43 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/recipes-bsp/images/
H A Dtc-artifacts-image.bb13 # The last image to be built is trusted-firmware-a
14 DEPENDS += " trusted-firmware-a"
/openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/
H A Dmusca-b1.md14 To build the trusted firmware-m:
15 ```bash$ bitbake trusted-firmware-m```
/openbmc/linux/security/integrity/ima/
H A DKconfig197 be signed and verified by a public key on the trusted IMA
210 and verified by a public key on the trusted IMA keyring.
222 and verified by a key on the trusted IMA keyring.
255 secondary trusted keyrings. The key must also have the
261 built-in or secondary trusted keyrings.
275 bool "Load X509 certificate onto the '.ima' trusted keyring"
280 loaded on the .ima trusted keyring. These public keys are
281 X509 certificates signed by a trusted key on the
283 loading from the kernel onto the '.ima' trusted keyring.
315 trusted boot based on IMA runtime policies.
/openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/trusted-firmware-a/
H A Dtrusted-firmware-a_2.12.0.bb1 require recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc
H A Dtrusted-firmware-a_2.11.0.bb1 require recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc
/openbmc/u-boot/board/rockchip/evb_rk3328/
H A DREADME31 > git clone https://github.com/ARM-software/arm-trusted-firmware.git
38 > cd arm-trusted-firmware
57 > cp arm-trusted-firmware/build/rk3328/release/bl31.bin rkbin/rk33

1234567891011