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

Use GitHub's new artifact attestation tools to put signatures in sigstore? #160

Open
Mr0grog opened this issue May 6, 2024 · 4 comments
Labels
enhancement New feature or request

Comments

@Mr0grog
Copy link
Member

Mr0grog commented May 6, 2024

GitHub recently released some fancy new “artifact attestation” actions that integrate with sigstore: https://github.blog/2024-05-02-introducing-artifact-attestations-now-in-public-beta/

If I understand correctly, these go into Sigstore’s public transparency log (since we are a public and not private project), which gives us nice, verifiable signatures for our sdists and wheels. (GitHub’s post talks about using the gh GitHub client to verify signatures, but again, IIUC, we should also be able to use cosign or other verfiers, too — this doesn’t seem super worthwhile if those don’t also work.)

There is also sigstore/gh-action-sigstore-python as documented over at PyPA: https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#signing-the-distribution-packages . I suspect the new GitHub thing will probably include some more valuable metadata or add new stuff to the GitHub UI, but it’s also possible these are completely equivalent for [public] use case.

Seems worth implementing, or at least investigating further, since it looks pretty simple to do.

@Mr0grog Mr0grog added the enhancement New feature or request label May 6, 2024
@Mr0grog
Copy link
Member Author

Mr0grog commented May 6, 2024

This discussion implies that something might show up somewhere (not clear where) in GH's UI when using this, which would be nice: https://github.com/orgs/community/discussions/122028#discussioncomment-9312273

@Mr0grog
Copy link
Member Author

Mr0grog commented May 13, 2024

Looks like this is getting built into hynek/build-and-inspect-python-package, which we use: hynek/build-and-inspect-python-package#122

Closing this, since I don’t think there’s much for us to do here.

@Mr0grog Mr0grog closed this as not planned Won't fix, can't repro, duplicate, stale May 13, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Unreleased in Wayback Roadmap May 13, 2024
@webknjaz
Copy link

@Mr0grog FYI I documented why it's better to use a separate job with elevated privileges over in hynek/build-and-inspect-python-package#105 (comment). (Also, you didn't enable that feature anyway, as it needs a setting and more privileges set)

@Mr0grog
Copy link
Member Author

Mr0grog commented Jun 24, 2024

Ah, thanks for noting the security concern! Re-opening this since publishing attestations should not be part of publishing, not building.

@Mr0grog Mr0grog reopened this Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Development

No branches or pull requests

2 participants