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

[REQUEST] Consider signing releases #1004

Open
ottok opened this issue Jan 3, 2025 · 0 comments
Open

[REQUEST] Consider signing releases #1004

ottok opened this issue Jan 3, 2025 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@ottok
Copy link
Contributor

ottok commented Jan 3, 2025

Thanks for working on btop!

This project uses rich releases at https://github.com/aristocratos/btop/releases

It is good practice in open source projects to publish cryptographic signatures alongside the tarball source releases, so that e.g. Linux distributions and other downstreams can use OpenPGP to verify the authenticity of the imported release.

This is not a hard requirement, just nice to have. Managing OpenPGP keys securely requires some effort. A good guide on the topic can be found at https://github.com/lfit/itpol/blob/master/protecting-code-integrity.md/

@ottok ottok added the enhancement New feature or request label Jan 3, 2025
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
None yet
Development

No branches or pull requests

2 participants