-
Notifications
You must be signed in to change notification settings - Fork 547
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
verify-blob
function should be implemented consistently with verify image function
#2222
Comments
I'll be working on one change to refactor and simplify the logic, TBA. |
Hey! We just released the security fixes and the code is refactored (and tested). If you rebase your PR (or might be easier to redo....) I think it'll be good to go! |
Thank you very much! @asraa |
I think it's totally done. The one thing required is that the interface provided here is a lot cleaner than the one currently in the pkg. Right now it's
I could switch that over to providing something like this, that was suggested in the issue, but the problem is that it doesn't capture CertChains/Bundles/etc well.
|
Happy to close that out for now; I think that clean-up will happen naturally over time |
Description
verify-blob
is now implemented in "cmd/cosign/cli/verify" package, but this is inconsistent withverify
.The core functions of
verify
such asVerifyImageSignature()
are implemented in "pkg/cosign", and it is easy for developers to invoke cosign's verification function from their own golang projects.However,
verify-blob
does not have this type of implementation, and developers need to callVerifyBlobCmd()
directly. This function requires some arguments that are filepath, and this makes it hard for developers to invoke verify-blob functions from some environment such as read-only container.The core functions of
verify-blob
should be inside "pkg/cosign" as well as verify image functions, and the functions should accept non-filepath arguments.(
VerifyBlobCmd()
will be just a wrapper which calls the core func in "pkg/cosign" in the new implementation.)Example
For example, something like below in "pkg/cosign" is what I am proposing in this issue.
The text was updated successfully, but these errors were encountered: