We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Github Artifact Attestation https://github.blog/changelog/2024-06-25-artifact-attestations-is-generally-available/ only uses public good rekor and fulcio for public repositories. For private repositories it supports usage of the following github hosted instances (note it does not use rekor):
https://fulcio.githubapp.com/ https://timestamp.githubapp.com/
It would be great if containers-sigstore-signing-params.yaml.5 supported a timestamp authority server in the config:
fulcio: fulcioURL: "https://fulcio.githubapp.com" oidcMode: "staticToken" oidcIDToken: "placeholder" timestampAuthorityURL: "https://timestamp.githubapp.com"
Refer to
The text was updated successfully, but these errors were encountered:
Thanks for your report.
More to the point, I think we should also want to accept signatures using a timestamp authority, not Rekor.
Sorry, something went wrong.
No branches or pull requests
Github Artifact Attestation https://github.blog/changelog/2024-06-25-artifact-attestations-is-generally-available/ only uses public good rekor and fulcio for public repositories.
For private repositories it supports usage of the following github hosted instances (note it does not use rekor):
https://fulcio.githubapp.com/
https://timestamp.githubapp.com/
It would be great if containers-sigstore-signing-params.yaml.5 supported a timestamp authority server in the config:
Refer to
The text was updated successfully, but these errors were encountered: