Searched refs:sign (Results 1 – 14 of 14) sorted by relevance
12 # ESBC Flag. Specify ESBC=0 to sign u-boot and ESBC=1 to sign ESBC images.(default is 0)
13 # ESBC Flag. Specify ESBC=0 to sign u-boot and ESBC=1 to sign ESBC images.(default is 0)63 # Specify the file names of hash file and sign file.65 INPUT_SIGN_FILENAME=sign.out
37 static int rsa_public_verif_sec(uint8_t *sign, uint8_t *to, in rsa_public_verif_sec() argument49 ctx.pkin.a = sign; in rsa_public_verif_sec()59 flush_dcache_range((uintptr_t)sign, klen); in rsa_public_verif_sec()
37 extensions. To sign the certificates, different signature schemes are available,41 certificates are used to verify public keys which have been used to sign content53 The private part of this key is used to sign the BL2 content certificate and58 The private part is used to sign the key certificates corresponding to the64 The private part is used to sign the key certificate corresponding to the71 sign the content certificate for the BL3X image. The public part is stored
313 #. A pointer to data to sign
35 personal information I submit with it, including my sign-off) is
390 WARNINGS += -Wshift-overflow -Wshift-sign-overflow \
79 s_a ^= s_b; // sign of quotient
5 this project are accepted under the same license with developer sign-off as
801 …- correct sign-compare warning ([ed38366](https://review.trustedfirmware.org/plugins/gitiles/TF-A/…1223 …- add sign-compare warning ([c10f3a4](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trus…
70 case you can simply sign the ELF image using a randomly generated key. You can
149 A further step is to sign BL2.
56 to sign the BL2 and Trusted Key certificates. Available options for
2315 sign Realm attestation token. The API currently only supports P-384 ECC curve
Completed in 27 milliseconds