Lines Matching full:verification

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)
216 1. SessionStat (to read back verification status)
237 1. SessionStat (to read back verification status)
363 If the image verification fails, it will automatically delete any files
510 verification step will return failure and the files will be deleted from the BMC
516 a valid signature. The expected result is that the verification step will return