-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] verification error during build for Go builder #657
Comments
Let's also add some e2e tests for all previous released builders. Nothing expressive, just a simple build. This way we will be alerted before our users if sigstore break backward compatibility. |
Yeah, that's right -- it's because old versions of cosign just had a faulty TUF client that couldn't handle any updates to the server. We've had to update the TUF server going forward, and this causes old clients (below 1.9.0) to break. I think the only thing possible is a patch release, either updating cosign's TUF client or potentially hard-coding the verification certificates, which is bad |
Gotcha. Patch release is the best way I suppose? But that won't help clients who don't update. Scorecard repo, for some reasons, is still using v1.0.0... I'm starting to wonder if dependabot knows about re-usable workflows or not... |
I think we probably have fixed this error but I think scorecards is failing with the TUF error in #1163. I think we are tracking that issue there so maybe we can close this issue? |
I think it's the same as well. |
Scorecard build failed https://github.com/ossf/scorecard/runs/7638656220?check_suite_focus=true:
Looks like it's about verification.
@asraa do you know what this is?
The text was updated successfully, but these errors were encountered: