Home
last modified time | relevance | path

Searched refs:verification (Results 1 – 25 of 107) sorted by relevance

12345

/openbmc/phosphor-ipmi-flash/bmc/firmware-handler/test/
H A Dfirmware_json_unittest.cpp34 "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 …]
H A Dcreate_action_map.hpp18 actionPack->verification = CreateTriggerMock(); in CreateActionMap()
H A Dfirmware_multiplebundle_unittest.cpp78 bmcPack->verification = std::move(bmcVerifyMock); in SetUp()
83 biosPack->verification = std::move(biosVerifyMock); in SetUp()
/openbmc/u-boot/cmd/ti/
H A DKconfig7 supports memory verification, memory comapre and ecc
8 verification if supported.
/openbmc/phosphor-ipmi-flash/bmc/firmware-handler/
H A Dfirmware_handlers_builder.cpp96 pack->verification = buildFileSystemd(verify); in buildHandlerFromJson()
100 pack->verification = buildSystemd(verify); in buildHandlerFromJson()
104 pack->verification = SkipAction::CreateSkipAction(); in buildHandlerFromJson()
H A Dconfig-static-bmc-reboot.json.in12 "verification": { object
H A Dconfig-static-bmc.json.in12 "verification": { object
H A Dconfig-bios.json.in12 "verification": { object
H A Dconfig-static-bmc-with-update-status.json.in12 "verification": { object
/openbmc/u-boot/doc/
H A DREADME.avb231 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/u-boot/doc/uImage.FIT/
H A Dverified-boot.txt6 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 Dipmi_flash.md60 **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 Dbmc_json_config.md34 "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 DREADME.md121 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. …
H A Dmeson.options112 description: 'The file checked for the verification status.',
124 description: 'The file checked for the verification status',
137 description: 'The systemd target started for verification',
/openbmc/openbmc/meta-google/recipes-phosphor/flash/dummy-gbmc-update/
H A Ddummy-verify.service2 Description=Dummy flash file verification
/openbmc/docs/designs/
H A Dfirmware-update-via-blobs.md43 - 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 Dredfish-tls-user-authentication.md202 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/u-boot/lib/rsa/
H A DKconfig8 verification in U-Boot.
27 algorithm used in FIT image verification. It required RSA Key as
/openbmc/openbmc/meta-inventec/meta-common/recipes-inventec/packagegroups/
H A Dpackagegroup-obmc-apps.bbappend6 #Install publickey for image file verification
/openbmc/openbmc/poky/meta/recipes-devtools/docbook-xml/
H A Ddocbook-xml-dtd4_4.5.bb1 SUMMARY = "Document type definitions for verification of XML data files"
2 DESCRIPTION = "Document type definitions for verification of XML data \
/openbmc/u-boot/board/xilinx/zynqmp/
H A DKconfig12 which is used for zynqmp secure image verification.
/openbmc/phosphor-dbus-monitor/mslverify/
H A DREADME.md5 verification.
/openbmc/openbmc/meta-google/recipes-phosphor/flash/
H A Dgoogle-key.bb23 # Install the verification helper
/openbmc/estoraged/include/
H A Dmeson.build23 # verification time.

12345