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

Feature Request: optional checksum verification #85

Closed
jqnatividad opened this issue Apr 14, 2022 · 2 comments · Fixed by #114
Closed

Feature Request: optional checksum verification #85

jqnatividad opened this issue Apr 14, 2022 · 2 comments · Fixed by #114

Comments

@jqnatividad
Copy link
Contributor

For additional security/peace of mind, it'd be great if self-update can check a release's checksum when its available, and only continue with the update if the checksum is verified.

@jaemk
Copy link
Owner

jaemk commented Apr 19, 2022

Yes, definitely would be a good addition!

@simonsan
Copy link

simonsan commented Nov 14, 2023

Can there be some insight, why zipsign has been used instead of for example minisign/rsign2 which cargo-binstall uses: https://github.com/cargo-bins/cargo-binstall/blob/main/SIGNING.md

Using zipsign means, that we would need to attach various different signatures to releases it seems, which is a bit unfortunate I would say instead of having a kind of standardized signing process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants