-
Notifications
You must be signed in to change notification settings - Fork 0
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
Generate build provenance attestations #28
Comments
That last link was most helpful to me. I've never been too concerned about verifying "artifacts" that I download over the Internet. Now that I have a better understanding of provenance attestation, my first thought was the static binaries we are distributing via clang-tools-pip use. This is where I'd start integrating proper attestation. Then we can use such attestation downstream in cpp-linter-action (or in clang-tools-pip itself)... Pypi does not support any form of digital signing (that in aware of). Just last year, they dropped their support for PGP signatures. |
To summarize your thoughts, we can at least start with this
maybe we do not need to verify attestation in cpp-linter-action because static binaries have verified in clang-tools-pip。 Digital signing seems to become a roadmap of Pypi pypi/warehouse#15871 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This is complete anyway, right? |
I removed - [ ] cpp-linter/clang-tools-static-binaries#24 from the above list since it already provides sha256 files and is not easy to switch GitHub attestations for now. We have generated GitHub attestations for our Python package publish, so it is completed. |
It looks like GitHub rolled out their own attestations in beta. I wonder if we could integrate with that. for more details below:
The text was updated successfully, but these errors were encountered: