Replies: 1 comment
-
Update: this is implemented since release 1.3.0 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As part of running a release, we publish
sha256
checksum files likefirecracker-v1.0.2-x86_64.tgz.sha256.txt
When trying to verify the checksum with standard tools we find that it fails:
However the SHAs actually match, but the comparison needs to be done by eye or like so:
diff <(sha256sum firecracker-v1.0.2-aarch64.tgz |awk '{print $1}') firecracker-v1.0.2-aarch64.tgz.sha256.txt
... which is neither intuitive nor user-friendly.
We would like to gather some feedback from community if anybody depends on this behavior. Otherwise we will start producing normal sha256 checksum files in the future.
Beta Was this translation helpful? Give feedback.
All reactions