Closed snoopy870 closed 1 month ago
Each release includes a base64-encoded checksum that can be used to verify the installation. A checksum is provided for each platform that Frame supports in a corresponding .yml
file:
latest-mac.yml
latest.yml
latest-linux.yml
Here are the release assets for each of these platforms from our latest release: https://github.com/floating/frame/releases/latest
To verify you need to calculate the sha512 checksum for the Frame installer you downloaded, then base64-encode that value and check that it matches the value in the corresponding .yml
file.
One way to do this is with the following command
sha512sum Frame-Setup-0.5.0-beta.22.exe | cut -f1 -d\ | xxd -r -p | base64
(Note that this shows the process using the Windows `.exe` installer. Substitute the filename with the name of the installer you downloaded.)
shasum -a 512 Frame-Setup-0.5.0-beta.22-arm64.dmg | cut -f1 -d\ | xxd -r -p | base64
There are also various tools to calculate the checksum both online and available for download. Keep in mind that the sum provided in the .yml
file is base64-encoded, so make sure yours is too when checking that they match.
The SHA-512 checksums for version 0.6.9 do not match the checksums contained in the YML files.
For example, Frame-0.6.9.dmg has an SHA-512 checksum of 7bbe2b47d83919a54358da796013efd4f53139e8dfedbbc0a77095a5b4f55fb06bc7c576adaa57f245ad696547cfe05ebf6d3f15259072be9cf2fdaaaac1fab7. This does not match any of he checkums in latest-mac.yml.
The same goes for latest-linux.yml. There is no match between any of these checksums or the latest Linux releases.
Has anyone else experienced this issue?