My commit earlier this morning (5b3fc452247124ac16fb24f64f86dbf83730e2e2)
broke SHA512 checking. It's checking the defined SHA512 hash with the
file's SHA1 hash, which will of course never match.
Luckily this is not a security issue as it can only ever result in a valid
file being rejected, not the other way around.
Fix the check to actually compare against the file's SHA512 checksum.
My commit earlier this morning (5b3fc452247124ac16fb24f64f86dbf83730e2e2) broke SHA512 checking. It's checking the defined SHA512 hash with the file's SHA1 hash, which will of course never match.
Luckily this is not a security issue as it can only ever result in a valid file being rejected, not the other way around.
Fix the check to actually compare against the file's SHA512 checksum.