Hello, there are a few references to verifying these releases in different issues, but the current release's checksum is either an HTTP 406 error or Not Found.
https://github.com/balena-io/etcher/releases/download/v1.5.45/SHASUMS256.txt
Are the checksums still on GitHub? If so, where?
I had a quick look at https://github.com/balena-io/etcher/releases/tag/v1.5.45 and it seems like there are checksums inside the latest*.yml files?
@zvin Maybe it'd be useful to have the CI process collate them into a single SHASUMS512.txt ?
A central location would be ideal, but that's not the checksum in latest.yml, it's the checksum in binary piped through base64.
This is the sha512 checksum :
86e6f73a03a96d073579bbb20b7b25a346ab6b20bcea204bb4b26b36370f90e35217f342de43e4b92fd25b73dbb3ff1165ce27b2800967211ddb0bc5fb98daa7
The value in latest.yml is the checksum (in binary) encoded in base64 :
openssl dgst -sha512 -binary balenaEtcher-Setup-1.5.45.exe | openssl enc -base64
| Source | Output |
| ------------- | ------------- |
| latest.yml | hub3OgOpbQc1ebuyC3slo0arayC86iBLtLJrNjcPkONSF/NC3kPkuS/SW3Pbs/8RZc4nsoAJZyEd2wvF+5japw== |
| sha512sum | 86e6f73a03a96d073579bbb20b7b25a346ab6b20bcea204bb4b26b36370f90e35217f342de43e4b92fd25b73dbb3ff1165ce27b2800967211ddb0bc5fb98daa7 |
| openssl dgst -sha512 -binary balenaEtcher-Setup-1.5.45.exe \| openssl enc -base64 | hub3OgOpbQc1ebuyC3slo0arayC86iBLtLJrNjcPkONSF/NC3kPkuS/SW3Pbs/8RZc4nsoAJZyEd2wvF+5japw== |
IMO, ideally the README.md should have the instructions spelled out for binary and piping to base64 with a link to the SHASUMS512.txt displayed prominently, to make the info accessible for all levels of enthusiasm.
[robertgzr] This issue has attached support thread https://jel.ly.fish/#/support-thread~a8289a98-5d41-46d0-becd-146936f96705
Most helpful comment
A central location would be ideal, but that's not the checksum in latest.yml, it's the checksum in binary piped through base64.
This is the sha512 checksum :
86e6f73a03a96d073579bbb20b7b25a346ab6b20bcea204bb4b26b36370f90e35217f342de43e4b92fd25b73dbb3ff1165ce27b2800967211ddb0bc5fb98daa7The value in latest.yml is the checksum (in binary) encoded in base64 :
openssl dgst -sha512 -binary balenaEtcher-Setup-1.5.45.exe | openssl enc -base64| Source | Output |
| ------------- | ------------- |
| latest.yml | hub3OgOpbQc1ebuyC3slo0arayC86iBLtLJrNjcPkONSF/NC3kPkuS/SW3Pbs/8RZc4nsoAJZyEd2wvF+5japw== |
|
sha512sum| 86e6f73a03a96d073579bbb20b7b25a346ab6b20bcea204bb4b26b36370f90e35217f342de43e4b92fd25b73dbb3ff1165ce27b2800967211ddb0bc5fb98daa7 ||
openssl dgst -sha512 -binary balenaEtcher-Setup-1.5.45.exe \| openssl enc -base64| hub3OgOpbQc1ebuyC3slo0arayC86iBLtLJrNjcPkONSF/NC3kPkuS/SW3Pbs/8RZc4nsoAJZyEd2wvF+5japw== |IMO, ideally the
README.mdshould have the instructions spelled out for binary and piping to base64 with a link to theSHASUMS512.txtdisplayed prominently, to make the info accessible for all levels of enthusiasm.