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

Why not using an empty configuration for the signature on OCI 1.1? #3750

Open
Silvanoc opened this issue Jun 25, 2024 · 1 comment
Open

Why not using an empty configuration for the signature on OCI 1.1? #3750

Silvanoc opened this issue Jun 25, 2024 · 1 comment
Labels
question Further information is requested

Comments

@Silvanoc
Copy link

Silvanoc commented Jun 25, 2024

Question

From what I see, the configuration file of the referrer containing the signature in OCI 1.1 format is needless. Why not using an empty one then, as foreseen by the spec? Please see here for guidance for an empty configuration.

The artifact is nevertheless not valid for container images, so keeping the configuration file for compliance with them is worthless.

@Silvanoc Silvanoc added the question Further information is requested label Jun 25, 2024
@Silvanoc
Copy link
Author

After looking at the part of the specification about "artifact usage", I am unsure if using an empty config ({}) with a media type other than application/vnd.oci.empty.v1+json (since that is the way cosign specifies the artifact type) is allowed. I'll try to clarify it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant