You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
📦 Supply Chain Security Related artifacts for an image: IMAGE
└── 🔐 Signatures for an image tag: index.docker.io/OWNER/CONTAINER:sha256-605350272bedf07cbb4efdb5b31b5c86c907be648fac1a2994f943abf1559fd3.sig
└── 🍒 sha256:0b6956fa9c4315ccf2be20fd5c9cd07a64a2a25a69f0d4b0cced59db4dc70a4d
└── 💾 Attestations for an image tag: index.docker.io/OWNER/CONTAINER:sha256-605350272bedf07cbb4efdb5b31b5c86c907be648fac1a2994f943abf1559fd3.att
└── 🍒 sha256:4b9c3ccef0ca5562b8950e4203879103df43e2ac7a083ebc5a1769c9a5a50aac
Error: getting Rekor public keys: unable to initialize client, local cache may be corrupt: tuf: error unmarshalling key: invalid PEM value
main.go:74: error during command execution: getting Rekor public keys: unable to initialize client, local cache may be corrupt: tuf: error unmarshalling key: invalid PEM value
The verification step is failing due to invalid PEM value, which is odd since the public key was generated on step 1 by cosign. I suspect I'm missing some initialization step here, however, cannot find what it is, any ideas as welcome.
The text was updated successfully, but these errors were encountered:
Hi, I'm using cosign v2.3.0 to add an SPDX SBOM as an attestation based on locally generated key-value pairs, following the steps described here: https://aquasecurity.github.io/trivy/v0.31.3/docs/attestation/sbom/#sign-with-a-local-key-pair
📦 Supply Chain Security Related artifacts for an image: IMAGE
└── 🔐 Signatures for an image tag: index.docker.io/OWNER/CONTAINER:sha256-605350272bedf07cbb4efdb5b31b5c86c907be648fac1a2994f943abf1559fd3.sig
└── 🍒 sha256:0b6956fa9c4315ccf2be20fd5c9cd07a64a2a25a69f0d4b0cced59db4dc70a4d
└── 💾 Attestations for an image tag: index.docker.io/OWNER/CONTAINER:sha256-605350272bedf07cbb4efdb5b31b5c86c907be648fac1a2994f943abf1559fd3.att
└── 🍒 sha256:4b9c3ccef0ca5562b8950e4203879103df43e2ac7a083ebc5a1769c9a5a50aac
The verification step is failing due to invalid PEM value, which is odd since the public key was generated on step 1 by cosign. I suspect I'm missing some initialization step here, however, cannot find what it is, any ideas as welcome.
The text was updated successfully, but these errors were encountered: