Add checksums to release files #14
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is to address an unopened issue similar to: gruntwork-io/terragrunt#610 The checksums of all binaries within `bin/` will be saved within `SHA256SUMS`. The integrity of binaries can now be verified with this command: `sha256sum --check --ignore-missing SHA256SUMS`. In the future, Gruntwork should consider using a PGP key to cryptographically sign this checksums file and to distribute the signature along with the rest of the release files. Doing so will likely require using private CI/CD infrastructure instead of CircleCI so that Gruntwork may have full control over their private signing key.
brikis98
approved these changes
Mar 4, 2019
|
Looks like that worked perfectly, thank you! https://github.com/gruntwork-io/health-checker/releases/tag/v0.0.4 |
This was referenced Mar 4, 2019
|
You're welcome! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is to address an unopened issue similar to:
gruntwork-io/terragrunt#610
The checksums of all binaries within
bin/will be saved withinSHA256SUMS. The integrity of binaries can now be verified with thiscommand:
sha256sum --check --ignore-missing SHA256SUMS.In the future, Gruntwork should consider using a PGP key to
cryptographically sign this checksums file and to distribute the
signature along with the rest of the release files. Doing so will likely
require using private CI/CD infrastructure instead of CircleCI so that
Gruntwork may have full control over their private signing key.