slsa-github-generator: [bug] "Generate builder" and "Run sigstore/cosign-installer" steps failing with `error updating to TUF remote mirror: invalid key`
The “Generate builder” and “Run sigstore/cosign-installer” steps have started failing for my workflows. This used to work fine, not sure if it is just an intermittent error or something more fundamental:
Here’s a build that worked 18 hours ago but is failing now (i.e. without any code changes): https://github.com/jkreileder/cf-ips-to-hcloud-fw/actions/runs/8339143012 (corresponding workflow)
Generate buildererror:
Verifying artifact slsa-generator-container-linux-amd64: FAILED: error retrieving Rekor public keys: updating local metadata and targets: error updating to TUF remote mirror: invalid key
remote status:{
"mirror": "https://tuf-repo-cdn.sigstore.dev/",
"metadata": {
"root.json": {
"version": 9,
"len": 6766,
"expiration": "12 Sep 24 06:53 UTC",
"error": ""
},
"snapshot.json": {
"version": 132,
"len": 2302,
"expiration": "09 Apr 24 16:16 UTC",
"error": ""
},
"targets.json": {
"version": 9,
"len": 5478,
"expiration": "12 Sep 24 06:13 UTC",
"error": ""
},
"timestamp.json": {
"version": 169,
"len": 723,
"expiration": "26 Mar 24 16:16 UTC",
"error": ""
}
}
}
FAILED: SLSA verification failed: error retrieving Rekor public keys: updating local metadata and targets: error updating to TUF remote mirror: invalid key
remote status:{
"mirror": "https://tuf-repo-cdn.sigstore.dev/",
"metadata": {
"root.json": {
"version": 9,
"len": 6766,
"expiration": "12 Sep 24 06:53 UTC",
"error": ""
},
"snapshot.json": {
"version": 132,
"len": 2302,
"expiration": "09 Apr 24 16:16 UTC",
"error": ""
},
"targets.json": {
"version": 9,
"len": 5478,
"expiration": "12 Sep 24 06:13 UTC",
"error": ""
},
"timestamp.json": {
"version": 169,
"len": 723,
"expiration": "26 Mar 24 16:16 UTC",
"error": ""
}
}
}
Error: Process completed with exit code 6.
Run sigstore/cosign-installer@6e04d228eb30da1757ee4e1dd75a0ec73a653e06error:
Error: getting ctlog public keys: updating local metadata and targets: error updating to TUF remote mirror: invalid key
remote status:{
"mirror": "https://tuf-repo-cdn.sigstore.dev/",
"metadata": {
"root.json": {
"version": 9,
"len": 6766,
"expiration": "12 Sep 24 06:53 UTC",
"error": ""
},
"snapshot.json": {
"version": 132,
"len": 2302,
"expiration": "09 Apr 24 16:16 UTC",
"error": ""
},
"targets.json": {
"version": 9,
"len": 5478,
"expiration": "12 Sep 24 06:13 UTC",
"error": ""
},
"timestamp.json": {
"version": 169,
"len": 723,
"expiration": "26 Mar 24 16:16 UTC",
"error": ""
}
}
}
main.go:74: error during command execution: getting ctlog public keys: updating local metadata and targets: error updating to TUF remote mirror: invalid key
remote status:{
"mirror": "https://tuf-repo-cdn.sigstore.dev/",
"metadata": {
"root.json": {
"version": 9,
"len": 6766,
"expiration": "12 Sep 24 06:53 UTC",
"error": ""
},
"snapshot.json": {
"version": 132,
"len": 2302,
"expiration": "09 Apr 24 16:16 UTC",
"error": ""
},
"targets.json": {
"version": 9,
"len": 5478,
"expiration": "12 Sep 24 06:13 UTC",
"error": ""
},
"timestamp.json": {
"version": 169,
"len": 723,
"expiration": "26 Mar 24 16:16 UTC",
"error": ""
}
}
}
Error: Process completed with exit code 1.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 5
- Comments: 23 (15 by maintainers)
Commits related to this issue
- Bump Cosign to latest v2.2.3 Versions of Cosign before v2.2.0 are not compatible with the latest TUF root. Fixes https://github.com/slsa-framework/slsa-github-generator/issues/3350 Signed-off-by: H... — committed to haydentherapper/slsa-github-generator by haydentherapper 3 years ago
- fix: Bump Cosign to latest v2.2.3 (#3355) Versions of Cosign before v2.2.0 are not compatible with the latest TUF root. Fixes https://github.com/slsa-framework/slsa-github-generator/issues/3350 ... — committed to slsa-framework/slsa-github-generator by haydentherapper 3 years ago
- chore: Update changelog for #3350 (#3401) # Summary Update changelog for #3350 ## Testing Process ... ## Checklist - [ ] Review the contributing [guidelines](./../CONTRIBUTING.md) - [... — committed to slsa-framework/slsa-github-generator by laurentsimon 3 years ago
- fix: Bump Cosign to latest v2.2.3 (#3355) Versions of Cosign before v2.2.0 are not compatible with the latest TUF root. Fixes https://github.com/slsa-framework/slsa-github-generator/issues/3350 ...... — committed to Ed-Fi-Alliance-OSS/slsa-github-generator by stephenfuqua 3 years ago
- Upgrade SLSA releaser due to github.com/slsa-framework/slsa-github-generator/issues/3350 — committed to ddworken/hishtory by ddworken 3 years ago
- Update release.yml SLSA breaking change requires an update of the action to 1.10: https://github.com/slsa-framework/slsa-github-generator/issues/3350 — committed to rsonquery/rsonpath by V0ldek 3 years ago
- build: bumping slsa-github-generator version to resolve issue with retrieving Rekor public keys (#386) Provenance generation fails due to Rekor public key errors were identified as a known issue and... — committed to launchdarkly/cpp-sdks by rsoberano-ld 3 years ago
- build: bumping slsa-github-generator version to resolve issue with retrieving Rekor public keys (#265) **Requirements** - [ ] I have added test coverage for new or changed functionality - [ ] I h... — committed to launchdarkly/ruby-server-sdk by rsoberano-ld 3 years ago
- build: bumping slsa-github-generator version to resolve issue with retrieving Rekor public keys (#280) **Requirements** - [ ] I have added test coverage for new or changed functionality - [ ] I h... — committed to launchdarkly/python-server-sdk by rsoberano-ld 3 years ago
- build: bumping slsa-github-generator version to resolve issue with retrieving Rekor public keys (#82) **Requirements** - [ ] I have added test coverage for new or changed functionality - [ ] I ha... — committed to launchdarkly/haskell-server-sdk by rsoberano-ld 3 years ago
- Update go-ossf-slsa3-publish.yml per https://github.com/slsa-framework/slsa-github-generator/issues/3350, SLSA needs to be updated to fix the TUF key error — committed to argonui/TTSModManager by argonui 2 years ago
- Upgrade SLSA releaser due to github.com/slsa-framework/slsa-github-generator/issues/3350 — committed to ddworken/hishtory by ddworken 3 years ago
- Optimize imports for extremely large history sizes for #168 (#171) * Swap to using iterators for uploading to avoid storing all chunks in memory * Chunk uploads for reuploading * Revert "Swap t... — committed to ddworken/hishtory by ddworken 2 years ago
- ci: update slsa-releaser; require go 1.20 ee https://github.com/slsa-framework/slsa-github-generator/issues/3350 — committed to bmflynn/cmrfetch by bmflynn 2 years ago
- Update generator-generic-ossf-slsa3-publish.yml Update workflow to use v1.10.0 as per https://github.com/slsa-framework/slsa-github-generator/issues/3350 — committed to arena-si-devops/rag-stock-transcript by jamesrgregg 2 years ago
- Bump SLSA provenance job image in build pipeline This should solve the error seen in the last build pipeline: 'error updating to TUF remote mirror: invalid key'. Assisted by: Cursor (powered by Clau... — committed to st3penta/review-rot by st3penta a year ago
- Bump SLSA provenance job image in build pipeline This should solve the error seen in the last build pipeline: 'error updating to TUF remote mirror: invalid key'. Assisted by: Cursor (powered by Clau... — committed to st3penta/review-rot by st3penta a year ago
Release is available v1.10.0 https://github.com/slsa-framework/slsa-github-generator/releases/tag/v1.10.0
Breaking changes are not something that is going to happen frequently and if they do, there will be a significant period of time to have clients migrate over.
@ddworken The latest version of slsa-verifier is still is able to verify old provenances. Why do you need to use an old version of slsa-verifier?
@haydentherapper @bobcallaway Probably unrelated to this issue but what is the Sigstore/Cosign solution for revoked root keys and in general how does Sigstore provide backward compatibility with old versions of certificates, and therefore verifying existing legitimate provenances that were signed with revoked keys?
We don’t expect this to happen. @haydentherapper can comment on the specifics of cosign.
@behnazh-w Supporting validity windows was the motivation behind the design of the trust root spec. For each root of trust, a validity time period is specified. If a compromise were to occur, rather than revoking the root material entirely and assuming we can determine the window when compromise occurred, the root material would simply be specified as valid only up to the compromise.
All Sigstore clients (eg sigstore-python, js, etc) but Cosign support ingesting the roots of trust in this format currently. Cosign will be updated to read it soon.
Works again for me with the un-finalized v1.10.0 pre-release.
Thank you @laurentsimon for being so responsive on this issue; I understand the commit auto-closed the bug. It’s helpful to have something to follow. Good luck and thank you for your hard work securing software supply chains.
Generator at main won’t pass verification. We need to cut the release. @kpk47 is working on it
Hi, yes let’s do that. I think we need to revert a few breaking PRs we made recently in the slsa-github-generator. slsa-verifier should be ready to be released. @ramonpetgrave64 could you send PRs to temporarily revert the few breaking PRs we made recently?
@laurentsimon @ianlewis I’m sorry to bother you, but could you release a new version of slsa-github-generator to solve this issue? https://github.com/slsa-framework/slsa-github-generator/issues/3350#issuecomment-2008731217