Home
last modified time | relevance | path

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

12

/u-boot/common/
A Dimage-fit-sig.c145 int verified = 0; in fit_image_verify_sig() local
168 verified = 1; in fit_image_verify_sig()
179 return verified ? 0 : -EPERM; in fit_image_verify_sig()
373 int verified = 0; in fit_config_verify_sig() local
388 verified = 1; in fit_config_verify_sig()
399 if (verified) in fit_config_verify_sig()
415 int verified = 0; in fit_config_verify_required_sigs() local
465 verified++; in fit_config_verify_required_sigs()
471 if (reqd_sigs && !verified) { in fit_config_verify_required_sigs()
A DKconfig.boot24 verified boot (secure boot using RSA).
85 using a hash signed and verified using RSA. If
101 This option sets a max size in bytes for verified FIT uImages.
383 bool "Support Chrome OS verified boot"
385 This is intended to enable the full Chrome OS verified boot support
/u-boot/doc/SPL/
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/
/u-boot/lib/efi_loader/
A Defi_signature.c303 bool verified = false; in efi_verify_certificate() local
327 verified = true; in efi_verify_certificate()
339 EFI_PRINT("%s: Exit, verified: %d\n", __func__, verified); in efi_verify_certificate()
340 return verified; in efi_verify_certificate()
445 bool verified = false; in efi_signature_verify() local
502 verified = true; in efi_signature_verify()
504 EFI_PRINT("%s: Exit, verified: %d\n", __func__, verified); in efi_signature_verify()
505 return verified; in efi_signature_verify()
/u-boot/doc/
A DREADME.chromium21 - Running U-Boot with Chromium OS verified boot. This allows U-Boot to be
30 - Running U-Boot and booting into a Chrome OS image, but without verified
34 U-Boot with Chromium OS verified boot
91 environment for new verified-boot features.
126 UCLASS_CROS_VBOOT_FLAG Chrome OS verified boot flag
154 Various options are available which control the operation of verified boot.
181 U-Boot without Chromium OS verified boot
187 # The offset 4f0 is defined by verified boot and may change for other
A DREADME.uniphier252 Please note the "u-boot.bin" must be signed, and verified by someone when it is
256 the system reset. If the Chain of Trust has a breakage somewhere, the verified
259 7. Boot verified kernel
A DREADME.update13 TFTP transfer is successful, the hash of each update is verified, and if the
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
A DREADME.socfpga24 verified with DE1_SOC_Linux_FB demo project (https://github.com/VCTLabs/DE1_SOC_Linux_FB).
A DREADME.POST485 The first 2 instructions (b, bl) will be verified by jumping to
634 following areas will be verified: 0x00000000-0x00000800,
680 features will be verified:
684 This will be verified by reading RTC in polling within a short
/u-boot/include/crypto/
A Dx509_parser.h40 bool verified; member
/u-boot/doc/uImage.FIT/
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:
198 'required' property, which tells U-Boot that this key must be verified for the
301 'dev' and the '+' means that it verified. If it showed '-' that would be bad.
303 Once the configuration is verified it is then possible to rely on the hashes
[all …]
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
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.
153 - required: If present this indicates that the key must be verified for the
155 normally verified by the FIT image booting algorithm. Valid values are
376 verified later even if the FIT has been signed with other keys in the
382 FITs are verified when loaded. After the configuration is selected a list
384 each image must be verified against those keys. This means that every image
392 - required-mode: Valid values are "any" to allow verified boot to succeed if
394 to allow verified boot to succeed if the selected configuration is signed by
[all …]
A Dx86-fit-boot.txt252 5. You can use verified/secure boot and other features which haven't yet been
/u-boot/arch/x86/include/asm/acpi/
A Dcros_gnvs.asl20 CHVD, 24576, // 0x19a - VDAT space filled by verified boot
/u-boot/drivers/tpm/
A DKconfig24 support Chrome OS verified boot. Extend functionality is not
138 verified boot. Cr50 is used on recent Chromebooks (since 2017).
/u-boot/drivers/misc/
A DKconfig166 keyboard (use the -l flag to enable the LCD), verified boot context,
168 enough to perform a Chrome OS verified boot on sandbox.
175 keyboard (use the -l flag to enable the LCD), verified boot context,
177 enough to perform a Chrome OS verified boot on sandbox.
184 keyboard (use the -l flag to enable the LCD), verified boot context,
186 enough to perform a Chrome OS verified boot on sandbox.
/u-boot/board/google/
A DKconfig73 U-Boot proper. This is useful where verified boot must select
/u-boot/arch/arm/dts/
A Drk3399-gru-chromebook.dtsi313 /* May run faster once verified. */
/u-boot/doc/board/emulation/
A Dqemu_capsule_update.rst81 capsule generation. This signature is then verified by using the
/u-boot/doc/arch/
A Dsandbox.rst183 commands, hashing, FIT images, verified boot and many other features are
507 verified boot:
/u-boot/doc/imx/habv4/
A Dintroduction_habv4.txt31 keys. The resulting signed image data is then verified on the i.MX processor
/u-boot/doc/board/sipeed/
A Dmaix.rst369 The FDT is verified after the kernel is relocated, so it must be loaded high
585 * The SHA-256 sum of the next stage is automatically calculated, and verified
/u-boot/doc/board/google/
A Dchromebook_coral.rst219 - Booting Chrome OS, e.g. with verified boot

Completed in 106 milliseconds

12