-
Notifications
You must be signed in to change notification settings - Fork 617
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
Migrate to/back-fill Sigstore bundles for Python releases #2300
Comments
I've created an archive of bundles from existing verification materials here: bundles.tar.gz This should be independently verified by a release manager and if found to be valid for each artifact we can upload the new bundles for existing releases. Hashes of the generated bundles in the archive are:
|
Verified the backfills were correct here: sethmlarson/verify-python-release-signatures@10a10da |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sigstore bundles is the new way to distribute verification materials which is better for verifiers because it allows for offline verification. Many older Python releases don't have bundles, but we can create the bundles from the existing verification materials.
I've created a script which creates a bundle from existing materials. We can then publish these new verification materials after independently verifying them against existing artifacts.
After all releases have a bundle associated with them we can update the Sigstore documentation to use bundles for verification instead of disconnected verification materials.
The text was updated successfully, but these errors were encountered: