Documentation ¶
Overview ¶
Package provenance provides tools for establishing the authenticity of a chart.
In Helm, provenance is established via several factors. The primary factor is the cryptographic signature of a chart. Chart authors may sign charts, which in turn provide the necessary metadata to ensure the integrity of the chart file, the Chart.yaml, and the referenced Docker images.
A provenance file is clear-signed. This provides cryptographic verification that a particular block of information (Chart.yaml, archive file, images) have not been tampered with or altered. To learn more, read the GnuPG documentation on clear signatures: https://www.gnupg.org/gph/en/manual/x135.html
The cryptography used by Helm should be compatible with OpenGPG. For example, you should be able to verify a signature by importing the desired public key and using `gpg --verify`, `keybase pgp verify`, or similar:
$ gpg --verify some.sig gpg: Signature made Mon Jul 25 17:23:44 2016 MDT using RSA key ID 1FC18762 gpg: Good signature from "Helm Testing (This key should only be used for testing. DO NOT TRUST.) <helm-testing@helm.sh>" [ultimate]
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Signatory ¶
type Signatory struct { // The signatory for this instance of Helm. This is used for signing. Entity *openpgp.Entity // The keyring for this instance of Helm. This is used for verification. KeyRing openpgp.EntityList }
Signatory signs things.
Signatories can be constructed from a PGP private key file using NewFromFiles or they can be constructed manually by setting the Entity to a valid PGP entity.
The same Signatory can be used to sign or validate multiple charts.
func NewFromFiles ¶
NewFromFiles constructs a new Signatory from the PGP key in the given filename.
This will emit an error if it cannot find a valid GPG keyfile (entity) at the given location.
Note that the keyfile may have just a public key, just a private key, or both. The Signatory methods may have different requirements of the keys. For example, ClearSign must have a valid `openpgp.Entity.PrivateKey` before it can sign something.
func NewFromKeyring ¶
NewFromKeyring reads a keyring file and creates a Signatory.
If id is not the empty string, this will also try to find an Entity in the keyring whose name matches, and set that as the signing entity. It will return an error if the id is not empty and also not found.
type SumCollection ¶
type SumCollection struct { Files map[string]string `json:"files"` Images map[string]string `json:"images,omitempty"` }
SumCollection represents a collection of file and image checksums.
Files are of the form:
FILENAME: "sha256:SUM"
Images are of the form:
"IMAGE:TAG": "sha256:SUM"
Docker optionally supports sha512, and if this is the case, the hash marker will be 'sha512' instead of 'sha256'.
type Verification ¶
type Verification struct { // SignedBy contains the entity that signed a chart. SignedBy *openpgp.Entity // FileHash is the hash, prepended with the scheme, for the file that was verified. FileHash string }
Verification contains information about a verification operation.