Home
last modified time | relevance | path

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

1234567

/openbmc/linux/crypto/asymmetric_keys/
H A Dpkcs7_trust.c40 if (x509->verified) in pkcs7_validate_trust_one()
41 goto verified; in pkcs7_validate_trust_one()
124 verified: in pkcs7_validate_trust_one()
126 x509->verified = true; in pkcs7_validate_trust_one()
128 p->verified = true; in pkcs7_validate_trust_one()
H A Dx509_parser.h37 bool verified; member
/openbmc/libpldm/tests/fuzz/
H A Dfd-fuzz.cpp58 bool verified; member
193 fuzz_ctx->verified = false; in cb_update_component()
226 assert(!fuzz_ctx->verified); in cb_firmware_data()
255 assert(!fuzz_ctx->verified); in cb_verify()
272 fuzz_ctx->verified = true; in cb_verify()
288 assert(fuzz_ctx->verified); in cb_apply()
/openbmc/u-boot/common/
H A Dimage-sig.c289 int verified = 0; in fit_image_verify_sig() local
304 verified = 1; in fit_image_verify_sig()
315 return verified ? 0 : -EPERM; in fit_image_verify_sig()
508 int verified = 0; in fit_config_verify_sig() local
523 verified = 1; in fit_config_verify_sig()
534 if (verified) in fit_config_verify_sig()
/openbmc/linux/fs/verity/
H A Dverify.c22 bool verified; in is_hash_block_verified() local
63 verified = test_bit(hblock_idx, vi->hash_block_verified); in is_hash_block_verified()
75 verified = false; in is_hash_block_verified()
78 return verified; in is_hash_block_verified()
/openbmc/u-boot/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/
/openbmc/linux/Documentation/admin-guide/device-mapper/
H A Dverity.rst127 Hash blocks are still verified each time they are read from the hash device,
129 blocks, and a hash block will not be verified any more after all the data
130 blocks it covers have been verified anyway.
151 dm-verity is meant to be set up as part of a verified boot path. This
157 After instantiation, all hashes will be verified on-demand during
158 disk access. If they cannot be verified up to the root node of the
168 corrupted data will be verified using the cryptographic hash of the
210 the command-line is verified.
/openbmc/linux/Documentation/firmware-guide/acpi/
H A Dchromeos-acpi-device.rst40 - Chrome OS verified boot data
284 - Offset in CMOS bank 0 of the verified boot non-volatile storage block, counting from
290 - Size in bytes of the verified boot non-volatile storage block.
306 VDTA (Chrome OS verified boot data)
308 This control method returns the verified boot data block shared between the firmware
317 A buffer containing the verified boot data block.
/openbmc/u-boot/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.
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
314 verified later even if the FIT has been signed with other keys in the
320 FITs are verified when loaded. After the configuration is selected a list
322 each image must be verified against those keys. This means that every image
355 Please see doc/uImage.FIT/verified-boot.txt for more information
/openbmc/qemu/crypto/
H A Dcipher-builtin.c.inc68 /* We have already verified that len % AES_BLOCK_SIZE == 0. */
84 /* We have already verified that len % AES_BLOCK_SIZE == 0. */
102 /* We have already verified that len % AES_BLOCK_SIZE == 0. */
124 /* We have already verified that len % AES_BLOCK_SIZE == 0. */
/openbmc/openbmc/poky/meta/recipes-core/initscripts/initscripts-1.0/
H A Dvolatiles1 # This configuration file lists filesystem objects that should get verified
21 # Thus, if a link is in the place to be verified, the object will be created
/openbmc/linux/tools/memory-model/scripts/
H A Dchecktheselitmus.sh41 echo All litmus tests verified as was expected. 1>&2
H A Dcheckalllitmus.sh63 echo All litmus tests verified as was expected. 1>&2
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-driver-chromeos-acpi132 Returns offset in CMOS bank 0 of the verified boot non-volatile
142 Return the size in bytes of the verified boot non-volatile
150 Returns the verified boot data block shared between the
H A Dsysfs-class-chromeos-driver-cros-ec-vbc5 Read/write the verified boot context data included on a
/openbmc/qemu/tests/qemu-iotests/
H A D265.out5 Content verified.
/openbmc/openbmc/meta-phosphor/recipes-phosphor/flash/noverify-bmc-update/
H A Dnoverify-bmc-verify.service6 ExecStart=/bin/mv /run/initramfs/bmc-image /run/initramfs/bmc-image-verified
H A Dnoverify-bmc-update.service6 ExecStart=/bin/mv /run/initramfs/bmc-image-verified /run/initramfs/image-bmc
/openbmc/linux/Documentation/admin-guide/sysctl/
H A Duser.rst26 verified to be below the per user limit in that user namespace.
30 in (user namespaces can be nested) and verified to be below the per user
/openbmc/linux/security/integrity/ima/
H A DKconfig197 be signed and verified by a public key on the trusted IMA
200 Kernel image signatures can not be verified by the original
210 and verified by a public key on the trusted IMA keyring.
212 Kernel module signatures can only be verified by IMA-appraisal,
222 and verified by a key on the trusted IMA keyring.
/openbmc/phosphor-power/phosphor-regulators/docs/config_file/
H A Dpmbus_write_vout_command.md59 … value of VOUT_COMMAND is verified by reading it from the device. If false or not specified, the u…
/openbmc/phosphor-state-manager/service_files/
H A Dobmc-powered-off@.service13 # verified that power has been removed from the chassis. Then
/openbmc/linux/Documentation/w1/slaves/
H A Dw1_ds2413.rst33 Bit 4-7: Complement of Bit 3 to Bit 0 (verified by the kernel module)

1234567