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)
142 Public keys should be stored as sub-nodes in a /signature node. Required
177 signature {
248 signature-1 {
250 value = <...kernel signature 1...>
255 signature-1 {
257 value = <...kernel signature 2...>
262 signature-1 {
264 vaue = <...fdt signature 1...>
269 signature-1 {
271 vaue = <...fdt signature 2...>
312 own hash, and we include the hash in the configuration signature.
352 signature-1 {
354 value = <...conf 1 signature...>;
360 signature-1 {
362 value = <...conf 1 signature...>;
370 longer signed), and a signature to each configuration. In the above example,
374 (so that it isn't possible to add or remove root nodes). The signature is
375 written into /configurations/conf-1/signature-1/value. It can easily be
390 the following optional property in /signature node in U-Boot's control FDT.
400 fdtput -t s control.dtb /signature required-mode any
401 fdtput -t s control.dtb /signature required-mode all
412 WARNING: When relying on signed FIT images with required signature check
615 Use the portion of the signature token URL after "pkcs11:" as the keydir argument (-k) to mkimage b…
658 - Enhance bootm to permit scripted signature verification (so that a script