Closed micolous closed 3 years ago
@Gridasov any idea?
Tried to investigate it - probably it was copy-paste from the previous version. Thank you - updated the hashes.
Actually found the root cause. The sha256 were correct - they are for the binaries inside the archive. After extraction try "sha256sum ./docker-credential-gcr" - this should give you the required checksum.
This is not fixed – the hashes on that page are still wrong (it just says "binary sha256sum", which is ambiguous as the sha256sum
command has a --binary
option).
I'm not aware of any open source project that publishes checksums for what is inside a tarball, rather than the tarball itself.
Please consider publishing a checksum file that can be checked with sha256sum -c
and including it in your release process.
Updated the release scripts, next time you will not see the binaries checksums) Forgot to update the release notes - done.
I downloaded all builds from https://github.com/GoogleCloudPlatform/docker-credential-gcr/releases/tag/v2.0.4, and run
sha256sum
over them, and get:The expected checksums according to that page are:
I tested this on my local machine, and from a brand-new "Google Cloud Container Optimised Linux" instance, both show the same result.