Add rekor support for cosign
See original GitHub issueDescribe the feature With #107, basic Cosign support was added. In the spirit of extending that support and strengthening the signature verification, we could extend this to also support the rekor integration of cosign: https://github.com/sigstore/cosign/tree/v0.2.0#rekor-support
Optional: Implementation ideas
We would probably have to extend the cosign configuration in the helm/values.yaml
and might reuse host
key. However, integration should not be too hard an issue.
Issue Analytics
- State:
- Created 2 years ago
- Comments:19
Top Results From Across the Web
Registry Support - Sigstore Documentation
Cosign uses go-containerregistry for registry interactions, which has generally excellent compatibility, but some registries may have quirks.
Read more >cosign latest · sigstore/cosign - Artifact Hub
Cosign supports : Hardware and KMS signing; Bring-your-own PKI; Our free OIDC PKI (Fulcio); Built-in binary transparency and timestamping service (Rekor) ...
Read more >sigstore / Cosign - CONNAISSEUR - Verify Container Image ...
Admission controller for Kubernetes integrating container image signature verification and trust pinning into a cluster to ensure that only valid images are ...
Read more >Signing Software The Easy Way with Sigstore and Cosign
In this article we will learn how cosign works and integrates with other sigstore components ( fulcio and rekor ). More importantly, we...
Read more >Keyless Sign and Verify Your Container Images With Cosign
As we've seen, signing your container images can be as trivial as a couple of lines added to your CI pipeline. If you're...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
issue opened: https://github.com/sigstore/cosign/issues/1816
neat 🙂 we’ll consider that when reworking the error handling, it may make things a bit messy though, but guess that’ll have to be seen