Lines Matching refs:transparency

13 transparency that leverages cryptographic proofs of inclusion of build images
41 transparency log key and the manufacturer key.
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
79 transparency logs. This allows the device manufacturer to not rely on a single
80 transparency log, and ensures that the builds represented by the VBMeta
86 included in a transparency log. An inclusion proof consists of three parts:
95 along with related metadata, which is signed by the transparency log’s private
105 1.  Given the set of hashes provided from the transparency log as part of the
107 can be found [here](https://www.certificate-transparency.org/log-proofs-work)
112 the public key of the transparency log that is stored on device. If the
125 for transparency checks at boot or system update time. This enhanced image is
138 the `AftlImage`, and validates them against a trusted transparency
172     a live transparency log.
198 inclusion proofs from transparency logs in the following manner:
215 is a part of the build fingerprint which allows for tagging the transparency
277 *  `--aftl_server`, the address of the transparency log
278 *  `--aftl_key_path`, which gives the path to the DER encoded transparency log public key
283 Remember that the public part of the transparency log keys need to be available
297 warning in case transparency checks fail.