Skip to content
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

Only one legacy cosign signature been replicated as accessory while several attached in the src artifact #20412

Open
MinerYang opened this issue May 10, 2024 · 1 comment

Comments

@MinerYang
Copy link
Contributor

MinerYang commented May 10, 2024

Description
When we are using legacy cosign singing images in a source Harbor and replicate into target Harbor instance, there's only one signature been attached to subject artifact in the target Harbor instance due to legacy cosign using specific tag sha256-<subject-digest-xxxx>.sig to reference its subject.Since only one signature remain tagged and could establish relationship with subject when pushing to target Harbor. While other signatures been untagged and replicated as individual artifacts.

Step1 signing a image several time using legacy cosign in the source harbor instance
Screenshot 2024-05-10 at 11 04 28

Step2 replicate to the target harbor instance

Step3 We will see only one signature with specific tag sha256-xxxxxx.sig been attached with subject artifact, the untagged one will been populate as an individual image in the UI.

Screenshot 2024-05-10 at 11 08 13
@wy65701436
Copy link
Contributor

In harbor, we only support a single signature using the default mode of cosign image signing. If you need to sign an artifact multiple times with cosign, please use the OCI 1.1 mode for signing the artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants