| /openbmc/phosphor-ipmi-flash/bmc/firmware-handler/test/ |
| H A D | firmware_json_unittest.cpp | 34 "verification" : { in TEST()
62 "verification" : { in TEST()
91 "verification" : { in TEST()
120 "verification" : { in TEST()
145 "verification" : { in TEST()
185 "verification" : { in TEST()
238 "verification" : { in TEST()
260 "verification" : { in TEST()
281 "verification" : { in TEST()
321 "verification" : { in TEST()
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Attestation/ |
| H A D | IdentityAuthentication.interface.yaml | 10 The status of the verification of the identity of the component.
34 The possible status of the verification.
38 Unsuccessful verification.
41 Successful verification.
|
| /openbmc/u-boot/test/py/tests/ |
| H A D | test_vboot.py | 9 For image verification:
11 - Check that verification shows that no keys are verified
13 - Check that verification shows that a key is now verified
15 For configuration verification:
18 - Check that image verification works
19 - Sign the FIT and mark the key as 'required' for verification
20 - Check that image verification works
22 - Check that image verification no-longer works
39 """Test verified boot signing with mkimage and verification with 'bootm'.
113 If the size is greater, the signature verification should return false.
|
| H A D | test_avb.py | 13 For configuration verification:
28 """Run AVB 2.0 boot verification chain with avb subset of commands
31 success_str = "Verification passed successfully"
|
| /openbmc/phosphor-ipmi-flash/bmc/firmware-handler/ |
| H A D | firmware_handler.hpp | 34 std::unique_ptr<TriggerableActionInterface> verification; member
86 /** The BMC is ready for verification or more bytes. */
88 /** The verification process has started, no more writes allowed. */
90 /** The verification process has completed. */
105 * @param[in] verification - pointer to object for triggering verification
119 * @param[in] verification - pointer to object for triggering verification
181 * verification, or preparing. This can happen if they open the hash in getActionPack()
233 /** Session for verification. */
|
| H A D | firmware_handlers_builder.cpp | 92 const auto& verify = a.at("verification"); in buildHandlerFromJson()
96 pack->verification = std::move(buildFileSystemd(verify)); in buildHandlerFromJson()
100 pack->verification = std::move(buildSystemd(verify)); in buildHandlerFromJson()
104 pack->verification = SkipAction::CreateSkipAction(); in buildHandlerFromJson()
109 "Invalid verification type:" + verifyType); in buildHandlerFromJson()
|
| /openbmc/u-boot/doc/ |
| H A D | README.avb2 | 31 Provides CLI interface to invoke AVB 2.0 verification + misc. commands for
35 avb verify - run verification process using hash data from vbmeta structure
53 Slot verification result: ERROR_IO
61 Slot verification result: ERROR_IO
83 echo AVB verification OK. Continue boot; \
86 echo AVB verification failed; \
|
| /openbmc/phosphor-ipmi-flash/tools/ |
| H A D | helper.hpp | 11 * Poll an open verification session.
13 * @param[in] session - the open verification session
15 * @return true if the verification was successful.
|
| H A D | handler.hpp | 37 * Trigger verification.
39 * @param[in] target - the verification blob id (may support multiple in the
41 * @param[in] ignoreStatus - determines whether to ignore the verification
43 * @return true if verified, false if verification errors.
|
| /openbmc/u-boot/doc/uImage.FIT/ |
| H A D | verified-boot.txt | 6 Verified boot here means the verification of all software loaded into a
27 made available without risk to the verification process. The private and
31 The signing and verification process looks something like this:
34 Signing Verification
48 +---------+ | * | verification |
68 the verification is worthless.
|
| H A D | signature.txt | 1 U-Boot FIT Signature Verification
28 The procedure for verification is:
38 image for the device. The verification is normally done in U-Boot on the
50 For the run-time verification side, it is important to keep code and data
53 For this reason the RSA image verification uses pre-processed public keys
150 is possible for the name to be changed. Verification can proceed by checking
156 "image" to force verification of all images, and "conf" to force verification
318 Verification
328 Enabling FIT Verification
333 CONFIG_FIT_SIGNATURE - enable signing and verification in FITs
[all …]
|
| /openbmc/docs/designs/ |
| H A D | firmware-update-via-blobs.md | 43 - Any update mechanism must allow for triggering an image verification step
56 verification step, access to the staged firmware image must not be still
74 a time. If the verification blob is open, the other blobs cannot be opened, and
75 likewise if a client has a data blob open, the verification blob cannot be
114 important to your verification service. The value provided will be written to a
120 #### Verification Blob
123 purpose is to trigger and monitor the firmware verification process. Therefore,
131 When the verification file is closed, if verification was completed
134 The verification process used is not defined by this design.
197 1. SessionStat (to read back verification status)
[all …]
|
| /openbmc/u-boot/cmd/ti/ |
| H A D | Kconfig | 7 supports memory verification, memory comapre and ecc
8 verification if supported.
|
| /openbmc/phosphor-ipmi-flash/ |
| H A D | bmc_json_config.md | 34 "verification": {
95 - `verification`
98 The `preparation`, `verification`, and `update` fields expect a `type` field,
108 In this configuration the `verification` type is `systemd`. This will query
109 systemd for the status of the verification unit to determine running, success,
133 "verification": {
167 "verification": {
220 target. For verification and update operations this will track the status of the
|
| H A D | ipmi_flash.md | 60 **The BMC is ready for verification or more bytes.**
74 **The verification process has started, no more writes allowed.**
82 **The verification process has completed.**
106 If verification fails, the state still transitions to `verificationCompleted`
|
| /openbmc/qemu/tests/qemu-iotests/tests/ |
| H A D | reopen-file | 61 if 'Pattern verification failed' in self.vm.get_log():
62 print('ERROR: Pattern verification failed:')
64 self.fail('qemu-io pattern verification failed')
74 # (Pattern verification will be checked by tearDown())
|
| /openbmc/phosphor-bmc-code-mgmt/bmc/ |
| H A D | image_verify.hpp | 114 * @brief Contains signature verification functions.
116 * verification functions for signed image.
137 * @brief Image signature verification function.
144 * @return true if signature verification was successful,
183 * @return true if signature verification was successful, false if not
207 * @return true if signature verification was successful, false if not
|
| /openbmc/phosphor-power/phosphor-regulators/src/actions/ |
| H A D | pmbus_write_vout_command_action.hpp | 58 * If desired, write verification can be performed. The value of VOUT_COMMAND
61 * WriteVerificationError is thrown. To perform verification, the device must
120 * Write verification will be performed if specified in the constructor.
163 * Returns whether write verification will be performed when writing to
166 * @return true if write verification will be performed, false otherwise
243 * Indicates whether write verification will be performed when writing to
|
| /openbmc/u-boot/doc/imx/habv4/csf_examples/mx6_mx7/ |
| H A D | csf_uboot.txt | 22 Verification index = 0
30 Verification index = 2
|
| /openbmc/openpower-pnor-code-mgmt/ |
| H A D | image_verify.hpp | 109 * @brief Contains signature verification functions.
111 * verification functions for signed image.
134 * @brief Image signature verification function.
141 * @return true if signature verification was successful,
180 * @return true if signature verification was successful, false if not
|
| /openbmc/u-boot/doc/imx/habv4/csf_examples/additional_images/ |
| H A D | csf_additional_images.txt | 22 Verification index = 0
30 Verification index = 2
|
| /openbmc/pldm/pldmtool/oem/ibm/ |
| H A D | oem_ibm_state_set.hpp | 21 /** @brief PLDM OEM IBM Verification possible state set values
57 {PLDM_OEM_IBM_VERIFICATION_STATE, "OEM IBM Verification State"},
70 /** @brief Map for PLDM OEM IBM verification state possible state values
|
| /openbmc/u-boot/lib/libavb/ |
| H A D | avb_slot_verify.h | 38 /* Various error handling modes for when verification fails using a
70 * avb_slot_verify() will continue verification efforts and |out_data|
180 * command-line options set (unless verification is disabled, see
223 * disable-verification' then the return value will be
256 /* Performs a full verification of the slot identified by |ab_suffix|
259 * partition must use hash verification). If not using A/B, pass an
267 * Verification includes loading and verifying data from the 'vbmeta',
282 * ignore verification errors which is something needed in the
|
| H A D | avb_kernel_cmdline_descriptor.h | 22 * cmdline will only be applied if hashtree verification is not
26 * will only be applied if hashtree verification is disabled
|
| /openbmc/u-boot/lib/rsa/ |
| H A D | Kconfig | 8 verification in U-Boot.
27 algorithm used in FIT image verification. It required RSA Key as
|