package aftl

Get desktop application:
View/edit binary Protocol Buffers messages

• rpc AddVBMeta (AddVBMetaRequest, AddVBMetaResponse)

  api.proto:88

  Insert a new VBMeta structure into the log. This request will effectively create 2 log entries: - VBMeta itself - Vendor annotations, which includes a reference to the VBMeta.

  message AddVBMetaRequest

  api.proto:27

  • bytes vbmeta = 1

    VBMeta structure as described in https://android.googlesource.com/platform/external/avb/+/master/README.md. In case of chained partitions, each VBMeta is added via a separate call. The default size for gRPC payload is about 4MB. We expect vbmeta to be in the order of 64kB.

  • bytes signed_vbmeta_primary_annotation = 2

    Serialized SignedVBMetaPrimaryAnnotation. This annotation contains the hash of the vbmeta structure. It is signed using the manufacturer key. See types/types.go.

  message AddVBMetaResponse

  api.proto:41

  • optional InclusionProof annotation_proof = 1

    Inclusion proof and the leaf that was added to the log, which contains the annotation on VBMeta. It is required to have the complete leaf to validate the inclusion proof. For on-device verification, only these first 2 fields are required to validate the inclusion.

  • bytes annotation_leaf = 2

  • optional InclusionProof vbmeta_proof = 3

    Inclusion proof and leaf that was added to the log, which contains the full vbmeta partition. These fields are NOT required for validation but can still be recorded by a vendor to prove that the complete VBMeta was submitted.

  • bytes vbmeta_leaf = 4

• rpc AnnotateVBMetaWithBuild (stream AnnotateVBMetaWithBuildResponse, AnnotateVBMetaWithBuildResponse)

  api.proto:91

  Upload (or copy) the complete firmware image.

  message AnnotateVBMetaWithBuildResponse

  api.proto:73

  • optional InclusionProof annotation_proof = 1

    Inclusion proof and leaf for the firmware image. The leaf contains the URL where the image was stored. It is not required for vendors to keep this information. However, this can be used for their records to ensure the correctness of the log.

  • bytes annotation_leaf = 2

• bytes signed_vbmeta_build_annotation = 1

  Serialized SignedVBMetaBuildAnnotation. This annotation contains the hash of the full build image. See types/types.go.

• bytes image_chunk = 2

  Bytes of the binary images. The hash value of the concatenation of these chunk is contained in SignedVBMetaBuildAnnotation. This is ignored if any of the requests origin_url is set.

• string origin_url = 3

  Origin location of image. It is used to get a copy of the binary image from another server (e.g., Google Cloud Storage).

Used in: AddVBMetaResponse, AnnotateVBMetaWithBuildResponse

• optional trillian.Proof proof = 1

• optional trillian.SignedLogRoot sth = 2