[feat]: Publish OS and Service Releases with SHA256 Hashes
Prerequisites
- [X] I have searched for existing issues that already suggest this feature, without success.
Describe the Feature Request
A hash ought to be published with each published asset
Describe the Use Case
This allows both the devs to verify they are looking at the same asset, as well as allowing a user to verify they have the asset that was published
Describe Preferred Solution
SHA256 is fine
Describe Alternatives
No response
Anything else?
No response
ACK
What's LOE here?
It just needs to be part of our release process. Run a sha256sum and a b3sum of eos.img, and update.img when cutting a tag.
same for s9pks
At the moment your guides suggest simple downloading the latest OS image and checking against a checksum. There is no PGP verification process that is suggested. You find with much of the other privacy/security orientated software. Otherwise great! Thanks.
It just needs to be part of our release process. Run a sha256sum and a b3sum of eos.img, and update.img when cutting a tag.
same for s9pks
@islandbitcoin @k0gen @chrisguida @Blu-J @elvece