Lines Matching refs:inclusion

13 transparency that leverages cryptographic proofs of inclusion of build images
15 cryptographic proofs, called inclusion proofs, on-device to allow for offline
36 integration into the log, the AFTL personality returns the inclusion proof back
37 to the `aftltool`, which in turn incorporates the inclusion proof with the
43 * **Transparency log key:** Used by Trillian to sign inclusion proofs. The
60 of inclusion proofs (`AftlIcpEntry`) represented by this structure. Each
61 inclusion proof has associated metadata, such as the transparency log URL. A
72 inclusion proof from a specific transparency log server for a given [VBMeta
74 given the corresponding transparency log public key. The inclusion proof
75 validation process is described in the [inclusion proofs](#inclusion-proofs)
78 *Note*: A single `AftlImage` can have multiple inclusion proofs from different
85 An inclusion proof allows a user to prove that a specific VBMeta structure is
86 included in a transparency log. An inclusion proof consists of three parts:
98 Validation of an inclusion proof can be performed with the following steps,
106 inclusion proof, attempt to recalculate the root hash. Details of the process
110 inclusion proof. If it matches, continue validation.
113 signature is valid, the inclusion proof is valid.
124 is to add an inclusion proof to an existing `vbmeta.img` to be used
136 inclusion proofs. That is, it loads the `vbmeta` partition, checks
137 the VBMeta structure signature, walks through each inclusion proof stored in
149   + An implementation of AFTL inclusion proof validation. This
198 inclusion proofs from transparency logs in the following manner:
284 to the bootloader of the device to validate the inclusion proofs.
295 The boot flow should ensure checking of the inclusion proofs independent of the
301 inclusion proofs (this is done by the `aftl_slot_verify` function). The result