| /u-boot/doc/usage/ |
| A D | mbr.rst | 11 mbr verify [interface] [device no] [partition list]
17 The mbr command lets users create or verify the MBR (Master Boot Record)
58 => mbr verify mmc 0
60 The verify sub-command is especially useful in the system update scripts:
64 => if mbr verify mmc 0; then
71 The 'mbr verify' returns 0 if the layout matches the one on the storage
89 | 0 | mbr verify was succesful |
91 | 1 | mbr verify was not succesful |
|
| /u-boot/common/ |
| A D | image-sig.c | 78 .verify = rsa_verify,
85 .verify = rsa_verify,
93 .verify = padding_pkcs_15_verify,
98 .verify = padding_pss_verify,
148 crypto_algos[i].verify += gd->reloc_off; in image_get_crypto_algo()
|
| A D | bootm.c | 80 images.verify = env_get_yesno("verify"); in bootm_start()
797 static image_header_t *image_get_kernel(ulong img_addr, int verify) in image_get_kernel() argument
817 if (verify) { in image_get_kernel()
878 hdr = image_get_kernel(img_addr, images->verify); in boot_get_kernel()
937 if (android_image_get_kernel(buf, images->verify, in boot_get_kernel()
981 images.verify = 1; in bootm_host_load_image()
|
| A D | image-fit-sig.c | 131 if (info.crypto->verify(&info, ®ion, 1, fit_value, fit_value_len)) { in fit_image_check_sig()
359 if (info.crypto->verify(&info, region, count, fit_value, in fit_config_check_sig()
|
| A D | image.c | 61 int verify);
606 int verify) in image_get_ramdisk() argument
625 if (verify) { in image_get_ramdisk()
1265 images->verify); in boot_get_ramdisk()
|
| /u-boot/cmd/ |
| A D | source.c | 52 int verify; in image_source_script() local
61 verify = env_get_yesno("verify"); in image_source_script()
79 if (verify) { in image_source_script()
136 if (verify) { in image_source_script()
|
| A D | ximg.c | 41 int verify; in do_imgextract() local
59 verify = env_get_yesno("verify"); in do_imgextract()
110 if (verify) { in do_imgextract()
160 if (verify) { in do_imgextract()
|
| A D | md5sum.c | 82 int verify = 0; in do_md5sum() local
93 verify = 1; in do_md5sum()
107 if (!verify) { in do_md5sum()
|
| /u-boot/doc/android/ |
| A D | avb2.rst | 42 avb verify - run verification process using hash data from vbmeta structure
58 => avb verify
66 => avb verify
89 Then add ``avb verify`` invocation to your android boot sequence of commands,
92 => avb_verify=avb init $mmcdev; avb verify;
109 If partitions you want to verify are slotted (have A/B suffixes), then current
110 slot suffix should be passed to ``avb verify`` sub-command, e.g.::
112 => avb verify _a
|
| A D | fastboot-protocol.rst | 123 "verify:%08x" Send a digital signature to verify the downloaded
|
| /u-boot/lib/rsa/ |
| A D | Makefile | 8 obj-$(CONFIG_$(SPL_TPL_)RSA_VERIFY) += rsa-verify.o rsa-checksum.o
|
| /u-boot/doc/uImage.FIT/ |
| A D | verified-boot.txt | 62 The public key from the signer allows us to verify and therefore trust
80 4. We use the master public key to verify the first-stage image. We then
81 use the secondary public key in the first-stage image to verify the second-
92 include hashes to verify images, so it is relatively straightforward to
|
| A D | beaglebone_vboot.txt | 309 There is a test in test/vboot which uses U-Boot's sandbox build to verify that
421 Verifying Hash Integrity ... sha1,rsa2048:devrsa_verify_with_keynode: RSA failed to verify: -13
422 rsa_verify_with_keynode: RSA failed to verify: -13
424 Failed to verify required signature 'key-dev'
442 sha1,rsa2048:devrsa_verify_with_keynode: RSA failed to verify: -13
443 rsa_verify_with_keynode: RSA failed to verify: -13
445 Failed to verify required signature 'key-dev'
458 the private key that you signed with so that it can verify any kernels that
467 Now you have a special U-Boot image with the public key. It can verify can
483 can use to verify against it. These values are obtained from the public key
[all …]
|
| /u-boot/board/rockchip/evb_rk3328/ |
| A D | README | 21 * load and verify ATF image
22 * load and verify U-Boot image
|
| /u-boot/doc/ |
| A D | README.esbc_validate | 20 used to verify signature.
35 verify the u-boot code, the subsequent chain of trust should also
|
| A D | README.armada-secureboot | 18 The Armada's trusted boot framework enables the SoC to cryptographically verify
30 key from it, and verify its SHA-256 hash against a SHA-256 stored in a eFuse
33 verify its RSA signature (contained in the header block as well) using the
35 * Choose a code signing key, and use it to verify the header block (excluding
68 are used to sign and verify the secured header and the
71 to sign and verify the array of CSKs.
150 2) Load the secured header, and verify its checksum.
157 7) Load the binary image to the main memory and verify its checksum.
|
| A D | README.POST | 404 This test will verify the CPU cache (L1 cache). The test will
416 This test will verify the following ALU instructions:
441 To verify these instructions the test will run them with
462 for result and so on. This will enable to verify all
488 register will be checked as well (using mfspr). To verify the bc
507 executing the instruction, the test will verify the contents of
513 the test will verify the value of the destination register and
529 To verify the data cache operation the following test scenarios will
581 To verify the instruction cache operation the following test
611 The memory test will verify RAM using sequential writes and reads
[all …]
|
| /u-boot/fs/btrfs/ |
| A D | disk-io.h | 49 int verify, u16 csum_type);
|
| A D | disk-io.c | 314 int verify, int silent, u16 csum_type) in __csum_tree_block_size() argument
323 if (verify) { in __csum_tree_block_size()
339 int csum_tree_block_size(struct extent_buffer *buf, u16 csum_size, int verify, in csum_tree_block_size() argument
342 return __csum_tree_block_size(buf, csum_size, verify, 0, csum_type); in csum_tree_block_size()
346 struct extent_buffer *buf, int verify) in csum_tree_block() argument
351 return csum_tree_block_size(buf, csum_size, verify, csum_type); in csum_tree_block()
|
| /u-boot/scripts/ |
| A D | setlocalversion | 48 head=$(git rev-parse --verify --short HEAD 2>/dev/null); then
|
| /u-boot/include/ |
| A D | image.h | 422 int verify; /* env_get("verify")[0] != 'n' */ member
1208 uint8_t arch, int verify);
1344 int (*verify)(struct image_sign_info *info, member
1351 int (*verify)(struct image_sign_info *info, member
1526 int android_image_get_kernel(const struct andr_img_hdr *hdr, int verify,
|
| /u-boot/board/rockchip/evb_rk3399/ |
| A D | README | 24 * load and verify ATF image
25 * load and verify U-Boot image
|
| /u-boot/lib/crypto/ |
| A D | Kconfig | 50 signature data and provides the ability to verify the signature.
|
| /u-boot/common/spl/ |
| A D | spl.c | 212 images.verify = 1; in spl_load_fit_image()
231 images.verify = 1; in spl_load_fit_image()
252 images.verify = 1; in spl_load_fit_image()
|
| /u-boot/doc/imx/mkimage/ |
| A D | mxsimage.txt | 163 The mxsimage can also verify and dump contents of an image. Use the following
164 syntax to verify and dump contents of an image:
|