| /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/tools/memory-model/scripts/ |
| H A D | judgelitmus.sh | 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/linux/kernel/trace/rv/ |
| H A D | Kconfig | 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/Documentation/trace/rv/ |
| H A D | runtime-verification.rst | 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
70 Falcone, Ylies, et al. *A taxonomy for classifying runtime verification tools.*
75 verification of the real-time Linux kernel.* Ph.D. Thesis, 2020.
[all …]
|
| H A D | index.rst | 9 runtime-verification.rst
|
| /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/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-ipmi-flash/bmc/firmware-handler/ |
| H A D | firmware_handlers_builder.cpp | 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()
|
| /openbmc/u-boot/cmd/ti/ |
| H A D | Kconfig | 7 supports memory verification, memory comapre and ecc
8 verification if supported.
|
| /openbmc/linux/Documentation/tools/rv/ |
| H A D | index.rst | 4 Runtime verification (rv) tool
7 **rv** tool provides the interface for a collection of runtime verification
|
| H A D | rv.rst | 21 for formal verification with a practical approach for complex systems.
28 verification (rv) monitors.
|
| /openbmc/linux/Documentation/security/ |
| H A D | digsig.rst | 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/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 …]
|
| H A D | btrfs.rst | 24 * Scrub (on-line checksum verification)
33 * Read/write metadata 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/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:
48 +---------+ | * | verification |
68 the verification is worthless.
|
| /openbmc/phosphor-ipmi-flash/ |
| 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`
|
| 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 | README.md | 121 are separately sent to the BMC for verification. The verification package source
126 is reported. This is because the image verification process can exceed 10
208 externally, as it doesn't implement any encryption or integrity verification.
253 … `/tmp/bmc.verify` | The file checked for the verification status. …
254 …phor-ipmi-flash-bmc-verify.target` | The systemd target started for verification. …
258 … `/tmp/bios.verify` | The file checked for the verification status. …
260 …phor-ipmi-flash-bios-verify.target` | The systemd target started for verification. …
|
| /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
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)
216 1. SessionStat (to read back verification status)
[all …]
|
| H A D | redfish-tls-user-authentication.md | 202 of _Boost.Beast/Boost.ASIO/OpenSSL_ as the certificate verification is being
230 OEM schema. The sequence of credential verification stays the same regardless of
231 configuration. Whitelist verification is always-on, because of Redfish
247 login credentials without password, so verification of user existence cannot be
278 4. Chain certificates verification - checking that chained certificates are
|
| /openbmc/linux/fs/verity/ |
| H A D | Kconfig | 27 hash), or (b) authenticity verification (comparing the hash
42 This option adds support for in-kernel verification of
47 alternatives (such as userspace signature verification, and
|
| /openbmc/linux/tools/verification/rv/ |
| H A D | README.txt | 4 complements classical exhaustive verification techniques (such as model
38 Documentation/trace/rv/runtime-verification.rst
|
| /openbmc/linux/security/integrity/ |
| H A D | Kconfig | 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/lib/rsa/ |
| H A D | Kconfig | 8 verification in U-Boot.
27 algorithm used in FIT image verification. It required RSA Key as
|