Configuring Cosign with Custom Components
This page contains instructions on how to configure Cosign to work with alternative components for Rekor, Fulcio, or the CT Log.
Verifying keyless signatures require verifying signatures from Rekor, material (SCTs) from the CT log, and certificates that chain up to Fulcio. The public keys and root certificates for these components are distributed through TUF repositories. By default, Cosign uses a TUF client that has an initial trust in an embedded root and then fetches updated verification material from our public-good-instance TUF repository created on the root-signing GitHub repository.
There are three options to configure Cosign to verify against custom components:
Use scaffolding to create a custom Sigstore stack. This provides a TUF root distributing verification material for the custom components, and pre-configured Cosign with the trust root.
Create a TUF repository yourself, using go-tuf or python-tuf’s repository writers. Instructions for how to configure this root is in this blog post. This script can be used to create a TUF repository from the custom Fulcio, Rekor, and CT log verification material.
As a last resort, you may also use the following environment variables to configure custom keys out of band.
|SIGSTORE_REKOR_PUBLIC_KEY||This specifies an out of band PEM-encoded public key to use for a custom Rekor.|
|SIGSTORE_ROOT_FILE||This specifies an out of band PEM-encoded X.509 certificate for a custom Fulcio root certificate.|
|SIGSTORE_CT_LOG_PUBLIC_KEY_FILE||This specifies an out of band PEM-encoded or DER formatted public key for a custom CT log.|