-
Notifications
You must be signed in to change notification settings - Fork 21
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
cli: verify digests #681
cli: verify digests #681
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but there are some test failures:
https://github.com/open-component-model/ocm/actions/runs/8144045884/job/22257282304?pr=681
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unit tests still failing
@@ -89,7 +91,9 @@ func (o *SignatureCommand) Run() (rerr error) { | |||
handler := comphdlr.NewTypeHandler(o.Context.OCM(), session, repo, comphdlr.OptionsFor(o)) | |||
sopts := signing.NewOptions(sign, signing.Resolver(repo, lookup.Resolver)) | |||
if !o.spec.sign { | |||
sopts.VerifySignature = true | |||
if len(sopts.SignatureNames) > 0 || sopts.Issuer != nil || sopts.Keyless { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the meaning of Keyless
? It looks odd: "if there is no key (aka. Keyless), then verify the signature" ... I don't get it
Description
Enable the cli command
verify component
to verify digests without signature validationWhat type of PR is this? (check all applicable)
Related Tickets & Documents
Screenshots
Added tests?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Added to documentation?
Checklist: