-
Notifications
You must be signed in to change notification settings - Fork 163
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
[Enhancement] Document the verification of attestations produced from private GitHub repositories #1435
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
@EtienneDufresne are you able to successfully verify your attestations with the conf you provided ? getting a weird
|
@julien-michaud yes I was able to verify GH private repo produced attestations with this policy. Maybe @vishal-chdhry would be able to help? I suggest pinging him on slack. |
Description
The verifying sigstore bundles section of the documentation is specific to public GitHub repositories where the official Sigstore instance is used.
If the attestation is produced from a private GitHub repo (and for a private artifact), the GitHub Sigstore instance is used and there are no transparency logs as stated here.
For kyverno to be able to verify such attestations, its helm values.yaml must have this override:
In the ClusterPolicy, the attestation keyless attestor entry's rekor value must be updated to point to the GitHub Signstore Fulcio instance and set to ignore the transparency logs:
Slack discussion
https://kubernetes.slack.com/archives/CLGR9BJU9/p1720769654925739
The text was updated successfully, but these errors were encountered: