You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 7, 2023. It is now read-only.
I think we should consider adding cryptographic digests for the files released in etcd. Commonly called SHA256SUMS files they can be easily generated using the common sha256sum tool on most systems
Besides being a useful practice for download verification I would also like to use the SHA256SUMS as a way to ensure the releases aren't tampered with and track when they are modified. There is a tool called rget that I have been building that can do this if you provide SHA256SUMS for your releases.
The rget tool also has a subcommand to make it easy to create SHA256SUMS for existing releases, just run:
I think we should consider adding cryptographic digests for the files released in etcd. Commonly called SHA256SUMS files they can be easily generated using the common
sha256sumtool on most systemsAlternatively, there are some release automation tools that can build these files automatically.
Besides being a useful practice for download verification I would also like to use the SHA256SUMS as a way to ensure the releases aren't tampered with and track when they are modified. There is a tool called rget that I have been building that can do this if you provide SHA256SUMS for your releases.
The rget tool also has a subcommand to make it easy to create SHA256SUMS for existing releases, just run:
If all of the @etcd-io/maintainers-etcd agree I can make this change and publish the SHA256SUMS for all of our older releases.