Lines Matching refs:signature

10 The signature feature allows the hash to be signed with a private key such
25    - sign the hash with a private key to produce a signature
26    - store the resulting signature in the FIT
32    - extract the signature from the FIT
34    - verify (with the public key) that the extracted signature matches the
83 The following properties are required in the FIT's signature node(s) to
86 signature@1, signature@2, etc.
97 - value: The signature data (e.g. 256 bytes for 2048-bit RSA)
139 Public keys should be stored as sub-nodes in a /signature node. Required
183 			signature@1 {
185 				value = <...kernel signature 1...>
190 			signature@1 {
192 				value = <...kernel signature 2...>
197 			signature@1 {
199 				vaue = <...fdt signature 1...>
204 			signature@1 {
206 				vaue = <...fdt signature 2...>
247 own hash, and we include the hash in the configuration signature.
287 			signature@1 {
289 				value = <...conf 1 signature...>;
295 			signature@1 {
297 				value = <...conf 1 signature...>;
305 longer signed), and a signature to each configuration. In the above example,
309 (so that it isn't possible to add or remove root nodes). The signature is
310 written into /configurations/conf@1/signature@1/value. It can easily be
333 WARNING: When relying on signed FIT images with required signature check
502 Use the portion of the signature token URL after "pkcs11:" as the keydir argument (-k) to mkimage b…
545 - Enhance bootm to permit scripted signature verification (so that a script