Searched refs:sign (Results 1 – 16 of 16) 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()
35 personal information I submit with it, including my sign-off) is
36 -Wno-type-limits -Wno-sign-compare \89 cc-flags-llvm-clang += -Wshift-overflow -Wshift-sign-overflow \
58 certificate's issuer but by the content of the certificate extensions. To sign63 certificates are used to verify public keys which have been used to sign content88 The private part of this key is used to sign the trusted boot firmware93 The private part is used to sign the key certificates corresponding to the99 The private part is used to sign the key certificate corresponding to the106 sign the content certificate for the BL3X image. The public part is stored
382 #. A pointer to data to sign
486 sign = self.get_sign_key(node)489 if sign or nv_ctr:492 if sign:497 f.write("\t\t\t\t.pk = &{},\n".format(self.extract_label(sign)))
79 s_a ^= s_b; // sign of quotient
5 this project are accepted under the same license with developer sign-off as
2361 sign Realm attestation token. The API currently only supports P-384 ECC curve2456 arg0: Pointer to the token sign request to be pushed to EL3.2488 resp: Pointer to the token sign response to get from EL3.2508 sign Realm attestation token. Typically, with delegated attestation, the private key is
2903 …- sign verification issue with invalid Key/Signature ([7731465](https://review.trustedfirmware.org…3377 …- el3 token sign during attestation ([6a88ec8](https://review.trustedfirmware.org/plugins/gitiles/…5639 …- change variable type to fix gcc sign conversion error ([3a3e0e5](https://review.trustedfirmware.…7319 …- correct sign-compare warning ([ed38366](https://review.trustedfirmware.org/plugins/gitiles/TF-A/…7741 …- add sign-compare warning ([c10f3a4](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trus…
149 A further step is to sign BL2.
129 case you can simply sign the ELF image using a randomly generated key. You can
68 to sign the BL2 and Trusted Key certificates. Available options for
1337 | sig_alg_id | 0 | uint32_t | Algorithm idenfier for the sign request.|