GoogleApi.ContainerAnalysis.V1alpha1.Model.PgpSignedAttestation (google_api_container_analysis v0.14.0) View Source
An attestation wrapper with a PGP-compatible signature. This message only supports
ATTACHED signatures, where the payload that is signed is included alongside the signature itself in the same file.
nil) - Type (for example schema) of the attestation payload that was signed. The verifier must ensure that the provided type is one that the verifier supports, and that the attestation payload is a valid instantiation of that type (for example by validating a JSON schema).
nil) - The cryptographic fingerprint of the key used to generate the signature, as output by, e.g.
gpg --list-keys. This should be the version 4, full 160-bit fingerprint, expressed as a 40 character hexadecimal string. See https://tools.ietf.org/html/rfc4880#section-12.2 for details. Implementations may choose to acknowledge "LONG", "SHORT", or other abbreviated key IDs, but only the full fingerprint is guaranteed to work. In gpg, the full fingerprint can be retrieved from the
fprfield returned when calling --list-keys with --with-colons. For example:
gpg --with-colons --with-fingerprint --force-v4-certs \ --list-keys email@example.com tru::1:1513631572:0:3:1:5 pub:...... fpr:::::::::24FF6481B76AC91E66A00AC657A93A81EF3AE6FB:Above, the fingerprint is
nil) - The raw content of the signature, as output by GNU Privacy Guard (GPG) or equivalent. Since this message only supports attached signatures, the payload that was signed must be attached. While the signature format supported is dependent on the verification implementation, currently only ASCII-armored (
--armorto gpg), non-clearsigned (
--clearsignto gpg) are supported. Concretely,
gpg --sign --armor --output=signature.gpg payload.jsonwill create the signature content expected in this field in