| /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/linux/Documentation/trace/rv/ |
| H A D | runtime-verification.rst | 2 Runtime Verification
5 Runtime Verification (RV) is a lightweight (yet rigorous) method that
6 complements classical exhaustive verification techniques (such as *model
19 *online* verification of a system, enabling the *reaction* for unexpected
26 A monitor is the central part of the runtime verification of a system. The
30 In Linux terms, the runtime verification monitors are encapsulated inside the
41 | (instrumentation) | | (verification) | | (specification) |
54 In addition to the verification and monitoring of the system, a monitor can
64 For further information about the principles of runtime verification and
67 Bartocci, Ezio, et al. *Introduction to runtime verification.* In: Lectures on
[all …]
|
| /openbmc/linux/kernel/trace/rv/ |
| H A D | Kconfig | 15 bool "Runtime Verification"
18 Enable the kernel runtime verification infrastructure. RV is a
20 exhaustive verification techniques (such as model checking and
26 Documentation/trace/rv/runtime-verification.rst
54 bool "Runtime verification reactors"
58 Enables the online runtime verification reactors. A runtime
|
| /openbmc/linux/tools/verification/rv/ |
| H A D | README.txt | 1 RV: Runtime Verification
3 Runtime Verification (RV) is a lightweight (yet rigorous) method that
4 complements classical exhaustive verification techniques (such as model
37 Runtime Verification:
38 Documentation/trace/rv/runtime-verification.rst
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | xfs-self-describing-metadata.rst | 12 scalability, but of verification of the filesystem structure. Scalabilty of the
15 is this very scalability that causes the verification problem.
50 verification of metadata values, looking for values that are in range (and hence
51 not detected by automated verification checks) but are not correct. Finding and
76 self identifying and we can do much more expansive automated verification of the
84 contain, a large amount of the manual verification work can be skipped.
129 present that the run-time verification is not detecting.
156 The verification is completely stateless - it is done independently of the
166 For read verification, the caller needs to specify the expected type of metadata
168 object matches what was expected. If the verification process fails, then it
[all …]
|
| /openbmc/linux/tools/testing/selftests/net/forwarding/ |
| H A D | ethtool_mm.sh | 49 # to verification frame) should be taken into consideration while the
52 # the link partner's verification frames.
56 # Wait for verification to finish
61 check_err "$?" "Verification did not succeed"
72 log_test "Manual configuration with verification: $tx to $rx"
96 check_err "$?" "Verification is not disabled"
106 log_test "Manual configuration without verification: $tx to $rx"
129 # Wait for verification to time out
134 check_fail "$?" "Verification succeeded when it shouldn't have"
145 log_test "Manual configuration with failed verification: $tx to $rx"
|
| /openbmc/linux/tools/memory-model/scripts/ |
| H A D | judgelitmus.sh | 16 # "HW" is the --hw argument. In addition, non-Sometimes verification
19 # in that file will be used to judge the assembly-language verification.
109 echo ' !!! Verification error' $litmus
112 echo ' !!! Verification error' >> $LKMM_DESTDIR/$litmusout 2>&1
122 echo " !!! Unexpected non-$outcome verification" $litmus
125 echo " !!! Unexpected non-$outcome verification" >> $LKMM_DESTDIR/$litmusout 2>&1
149 echo " $flag non-$outcome verification" $litmus
152 echo " $flag non-$outcome verification" >> $LKMM_DESTDIR/$litmusout 2>&1
|
| /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.
|
| /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/linux/crypto/asymmetric_keys/ |
| H A D | Kconfig | 9 verification.
22 If signature generation and/or verification are to be used,
69 bool "Support for PE file signature verification"
80 tristate "Run FIPS selftests on the X.509+PKCS7 signature verification"
83 verification code, using some built in data. This is required
|
| /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/linux/kernel/ |
| H A D | Kconfig.kexec | 59 verification for the corresponding kernel image type being
67 This option makes kernel signature verification mandatory for
71 bool "Enable Image signature verification support (ARM)"
77 Enable Image signature verification support.
80 bool "Enable bzImage signature verification support"
86 Enable bzImage signature verification support.
|
| /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/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/linux/Documentation/tools/rv/ |
| H A D | rv.rst | 7 Runtime Verification
20 Runtime Verification (**RV**) is a lightweight (yet rigorous) method argument
21 for formal verification with a practical approach for complex systems.
28 verification (rv) monitors.
|
| /openbmc/linux/Documentation/security/ |
| H A D | digsig.rst | 2 Digital Signature Verification API
19 Digital signature verification API provides a method to verify digital signature.
22 Digital signature verification is implemented using cut-down kernel port of
58 digsig_verify() - digital signature verification with public key
62 * digsig_verify() - digital signature verification with public key
|
| /openbmc/linux/security/integrity/ |
| H A D | Kconfig | 10 Measurement Architecture (IMA), Extended Verification Module
11 (EVM), IMA-appraisal extension, digital signature verification
20 bool "Digital signature verification using multiple keyrings"
25 This option enables digital signature verification support
42 This option enables digital signature verification using
|
| /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/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
|
| /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-ipmi-flash/tools/ |
| 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.
|
| 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.
|
| /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
|