Home
last modified time | relevance | path

Searched refs:verify (Results 1 – 12 of 12) sorted by relevance

/mcuboot-3.7.0/scripts/imgtool/keys/
Decdsa.py175 def verify(self, signature, payload): member in ECDSA256P1Public
181 return k.verify(signature=signature, data=payload,
248 def verify(self, signature, payload): member in ECDSA384P1Public
254 return k.verify(signature=signature, data=payload,
Decdsa_test.py88 k.key.public_key().verify(
95 k.key.public_key().verify,
Ded25519_test.py92 k.key.public_key().verify(signature=sig, data=digest)
99 k.key.public_key().verify,
Drsa_test.py120 k.key.public_key().verify(
128 k.key.public_key().verify,
Drsa.py76 def verify(self, signature, payload): member in RSAPublic
80 return k.verify(signature=signature, data=payload,
Ded25519.py65 return k.verify(signature=signature, data=digest)
Dx25519.py119 return k.verify(signature=signature, data=digest)
/mcuboot-3.7.0/scripts/imgtool/
Dmain.py215 def verify(key, imgfile): function
217 ret, version, digest = image.Image.verify(imgfile, key)
524 imgtool.add_command(verify)
Dimage.py641 def verify(imgfile, key): member in Image
693 key.verify(tlv_sig, payload)
/mcuboot-3.7.0/docs/
Dreadme-espressif.md204 MCUboot will then verify and compare the new image version number with the current one before
406 Secure boot uses a signature block appended to the bootloader image in order to verify the
413 1. On startup, since it is the first boot, the ROM bootloader will not verify the bootloader image
422 will verify the MCUboot bootloader image. The process of an usual boot:
433 3. Use the public key to verify the signature of the bootloader image, using RSA-PSS with the
Dimgtool.md21 should match what MCUboot is configured to verify.
Drelease-notes.md257 - imgtool: Print image digest during verify.