| /u-boot/boot/ |
| A D | image-fit-sig.c | 144 int verified = 0; in fit_image_verify_sig() local
167 verified = 1; in fit_image_verify_sig()
178 return verified ? 0 : -EPERM; in fit_image_verify_sig()
420 int verified = 0; in fit_config_verify_key() local
436 verified = 1; in fit_config_verify_key()
447 if (verified) in fit_config_verify_key()
476 int verified = 0; in fit_config_verify_required_keys() local
533 verified++; in fit_config_verify_required_keys()
539 if (reqd_sigs && !verified) { in fit_config_verify_required_keys()
|
| /u-boot/doc/SPL/ |
| A D | README.spl-secure-boot | 1 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/ecdsa/ |
| A D | Kconfig | 16 Allow ECDSA signatures to be recognized and verified in U-Boot.
22 Allow ECDSA signatures to be recognized and verified in SPL.
|
| /u-boot/lib/efi_loader/ |
| A D | efi_signature.c | 366 bool verified = false; in efi_verify_certificate() local
390 verified = true; in efi_verify_certificate()
402 EFI_PRINT("%s: Exit, verified: %d\n", __func__, verified); in efi_verify_certificate()
403 return verified; in efi_verify_certificate()
510 bool verified = false; in efi_signature_verify() local
568 verified = true; in efi_signature_verify()
570 EFI_PRINT("%s: Exit, verified: %d\n", __func__, verified); in efi_signature_verify()
571 return verified; in efi_signature_verify()
|
| /u-boot/doc/chromium/ |
| A D | run_vboot.rst | 6 Running U-Boot with Chromium OS verified boot
74 environment for new verified-boot features.
118 Chrome OS verified boot flag
146 Various options are available which control the operation of verified boot.
173 U-Boot without Chromium OS verified boot
180 # The offset 4f0 is defined by verified boot and may change for other
|
| A D | overview.rst | 24 - Running U-Boot with Chromium OS verified boot. This allows U-Boot to be
33 - Running U-Boot and booting into a Chrome OS image, but without verified
40 Here is some material relevant to Chromium OS verified boot with U-Boot:
|
| /u-boot/doc/usage/fit/ |
| A D | index.rst | 17 verified-boot
|
| A D | beaglebone_vboot.rst | 9 Before reading this, please read :doc:`verified-boot` and :doc:`signature`.
13 verified boot works in U-Boot. There is also a test which runs through the
18 for an example of how to enable verified boot using U-Boot.
24 packaged with the kernel. In particular this is important with verified boot,
26 public keys can be changed and verified boot is useless. An attacker can
39 #. Build U-Boot for the board, with the verified boot options enabled.
70 b. Configure and build U-Boot with verified boot enabled::
308 'dev' and the '+' means that it verified. If it showed '-' that would be bad.
310 Once the configuration is verified it is then possible to rely on the hashes
314 hash verified. This means that none of the images has been tampered with.
[all …]
|
| A D | verified-boot.rst | 19 which use verified boot. Since the machine will only run software that has
30 be verified using a public key. As its name suggests the public key can be
102 a standard place. Then when a FIT is loaded it can be verified using that
|
| A D | signature.rst | 14 that it can be verified using a public key later. Provided that the private
16 any image can be verified in this way.
18 See verified-boot.txt for more general information on verified boot.
106 If present this indicates that the key must be verified for the
108 normally verified by the FIT image booting algorithm. Valid values are
349 verified later even if the FIT has been signed with other keys in the
391 FITs are verified when loaded. After the configuration is selected a list
393 each image must be verified against those keys. This means that every image
402 Valid values are "any" to allow verified boot to succeed if
404 to allow verified boot to succeed if the selected configuration is signed by
[all …]
|
| /u-boot/include/crypto/ |
| A D | x509_parser.h | 40 bool verified; member
|
| /u-boot/arch/x86/include/asm/acpi/ |
| A D | cros_gnvs.asl | 20 CHVD, 24576, // 0x19a - VDAT space filled by verified boot
|
| /u-boot/drivers/tpm/ |
| A D | Kconfig | 24 support Chrome OS verified boot. Extend functionality is not
138 verified boot. Cr50 is used on recent Chromebooks (since 2017).
148 verified boot. Cr50 is used on recent Chromebooks (since 2017).
158 verified boot. Cr50 is used on recent Chromebooks (since 2017).
168 verified boot. Cr50 is used on recent Chromebooks (since 2017).
|
| /u-boot/doc/develop/ |
| A D | vbe.rst | 10 how firmware and Operating Systems are located, updated and verified.
|
| A D | spl.rst | 90 if A/B verified boot is enabled. Implementation of the VPL logic is
|
| /u-boot/drivers/misc/ |
| A D | Kconfig | 224 keyboard (use the -l flag to enable the LCD), verified boot context,
226 enough to perform a Chrome OS verified boot on sandbox.
233 keyboard (use the -l flag to enable the LCD), verified boot context,
235 enough to perform a Chrome OS verified boot on sandbox.
242 keyboard (use the -l flag to enable the LCD), verified boot context,
244 enough to perform a Chrome OS verified boot on sandbox.
251 keyboard (use the -l flag to enable the LCD), verified boot context,
253 enough to perform a Chrome OS verified boot on sandbox.
|
| /u-boot/drivers/fastboot/ |
| A D | Kconfig | 102 feature if you are using verified boot, as it will allow an attacker
241 this feature if you are using verified boot, as it will allow an
|
| /u-boot/doc/android/ |
| A D | fastboot.rst | 235 fastboot can be used to update systems using verified boot. However, such
236 functionality can be useful for production or when verified boot is not in use.
|
| /u-boot/doc/ |
| A D | README.uniphier | 252 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 D | README.update | 13 TFTP transfer is successful, the hash of each update is verified, and if the
|
| A D | README.armada-secureboot | 90 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
|
| /u-boot/doc/usage/cmd/ |
| A D | source.rst | 187 disabled as these images cannot be signed and verified.
|
| /u-boot/board/google/ |
| A D | Kconfig | 85 U-Boot proper. This is useful where verified boot must select
|
| /u-boot/doc/board/siemens/ |
| A D | iot2050.rst | 100 To enable verified boot for the firmware artifacts after the Siemens-managed
|
| /u-boot/arch/arm/dts/ |
| A D | rk3399-gru-chromebook.dtsi | 313 /* May run faster once verified. */
|