As a user I, while mirroring, can verify image signature by providing verification policy config
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 31
- Forks
- 56
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 22
Description
Author: @ipanova (ipanova@redhat.com)
Redmine Issue: 9508, https://pulp.plan.io/issues/9508
Signatures are verified but not saved unless explicitly specified with-signature=True
If signature-verify=True was specified, the image signature will be verified against provided verification policy.
Only images that pass signature verification will be saved.
See https://github.com/containers/skopeo/blob/main/docs/skopeo-standalone-verify.1.md
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the container mirroring entry point that handles signature-verify=True and with-signature=True, then read the linked skopeo standalone-verify documentation for verification-policy context. Done means a supplied verification policy is applied during mirroring and only images that pass verification are saved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100