-
Notifications
You must be signed in to change notification settings - Fork 86
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
notation sign/verify to work with local storage #283
Comments
Sharing a proposal here - https://hackmd.io/5PmzMOcrSRaCUJzuy_Gbhg |
@FeynmanZhou @yizha1 @vaninrao10 is this something we can consider for rc.2? |
@toddysm - the bigger user story is set for RC2, but needs more clarity on scope. Please comment more on this thread which aspect of "local" you desire. |
Update the milestone to rc-3 based on the discussion. |
Working on this item, design in progress. |
This PR adds local sign/list/verification for OCI image layout directory. For RC.4: 1. It only supports storing the generated signature into the target OCI layout directory. 2. It supports listing signatures within the OCI layout directory. 3. It only supports verifying signatures within the target OCI layout directory. This PR is based on spec PR: #601 (Merged). This PR is dependent on the corresponding notation-go PR: notaryproject/notation-go#288. Please review the notation-go PR first. Resolves #283. Both remote registry and oci-layout scenario are tested. E2E tests are also included. --------- Signed-off-by: Patrick Zheng <[email protected]>
Implement notation to work with signatures in the local storage/filesystem.
The text was updated successfully, but these errors were encountered: