Home
last modified time | relevance | path

Searched refs:verified (Results 1 – 18 of 18) sorted by relevance

/rk3399_rockchip-uboot/doc/SPL/
H A DREADME.spl-secure-boot1 Overview of SPL verified boot on powerpc/mpc85xx & arm/layerscape platforms
7 This document provides an overview of how SPL verified boot works on powerpc/
/rk3399_rockchip-uboot/common/
H A Dimage-sig.c266 int verified = 0; in fit_image_verify_sig() local
281 verified = 1; in fit_image_verify_sig()
292 if (verified) in fit_image_verify_sig()
460 int verified = 0; in fit_config_verify_sig() local
475 verified = 1; in fit_config_verify_sig()
486 if (verified) in fit_config_verify_sig()
H A DKconfig262 This disable CLI interactive in verified-boot.
634 If enabled, adds support the android verified boot. The avb get the
643 If enabled, support the android verified boot rollback index.
/rk3399_rockchip-uboot/doc/uImage.FIT/
H A Dbeaglebone_vboot.txt7 Before reading this, please read verified-boot.txt and signature.txt. These
11 verified boot works in U-Boot. There is also a test which runs through the
16 for an example of how to enable verified boot using U-Boot.
22 packaged with the kernel. In particular this is important with verified boot,
24 public keys can be changed and verified boot is useless. An attacker can
37 1. Build U-Boot for the board, with the verified boot options enabled.
68 b. Configure and build U-Boot with verified boot enabled:
199 'required' property, which tells U-Boot that this key must be verified for the
302 'dev' and the '+' means that it verified. If it showed '-' that would be bad.
304 Once the configuration is verified it is then possible to rely on the hashes
[all …]
H A Dverified-boot.txt16 which use verified boot. Since the machine will only run software that has
26 be verified using a public key. As its name suggests the public key can be
96 a standard place. Then when a FIT is loaded it can be verified using that
H A Dsignature.txt11 that it can be verified using a public key later. Provided that the private
13 any image can be verified in this way.
15 See verified-boot.txt for more general information on verified boot.
150 - required: If present this indicates that the key must be verified for the
152 normally verified by the FIT image booting algorithm. Valid values are
311 verified later even if the FIT has been signed with other keys in the
317 FITs are verified when loaded. After the configuration is selected a list
319 each image must be verified against those keys. This means that every image
352 Please see doc/uImage.FIT/verified-boot.txt for more information
H A Dx86-fit-boot.txt252 5. You can use verified/secure boot and other features which haven't yet been
/rk3399_rockchip-uboot/drivers/tpm/
H A DKconfig13 support Chrome OS verified boot. Extend functionality is not
/rk3399_rockchip-uboot/doc/
H A DREADME.update13 TFTP transfer is successful, the hash of each update is verified, and if the
H A DREADME.socfpga24 verified with DE1_SOC_Linux_FB demo project (https://github.com/VCTLabs/DE1_SOC_Linux_FB).
H A DREADME.armada-secureboot90 images are verified (non-secure images won't boot);
96 Trusted boot framework - The ARMADA SoC's implementation of a secure verified
162 NOTE: All RSA signatures are verified according to the PKCS #1 v2.1 standard
H A DREADME.imx6147 be verified through High Assurance Boot (HAB).
H A DREADME.POST496 The first 2 instructions (b, bl) will be verified by jumping to
645 following areas will be verified: 0x00000000-0x00000800,
691 features will be verified:
695 This will be verified by reading RTC in polling within a short
H A DREADME.x861130 - Chrome OS verified boot
/rk3399_rockchip-uboot/drivers/misc/
H A DKconfig190 keyboard (use the -l flag to enable the LCD), verified boot context,
192 enough to perform a Chrome OS verified boot on sandbox.
/rk3399_rockchip-uboot/board/sandbox/
H A DREADME.sandbox154 commands, hashing, FIT images, verified boot and many other features are
386 verified boot
/rk3399_rockchip-uboot/
H A DKconfig194 verified boot (secure boot using RSA).
231 using a hash signed and verified using RSA. If
/rk3399_rockchip-uboot/cmd/
H A DKconfig746 sequence of I/O accesses can be verified.