Closed Doryforos closed 8 years ago
I'm not sure how to publish these on the release page, but here are the hashes for the Windows ZIP:
MD5 047ff5311d821f667150f37695bd01b3 SHA256 d5e85933e74e5ba6a73f67346bc2e765075d26949c831a428166c92772f67dbc
Thank you very much!
Why not publish the hash(-es) in the README.md file, though?
All the best!
P.S. Oh! ... And create a sha512deep, perhaps? [Mozilla Firefox, Filezilla, some Linux distributions e.a. only publish SHA512 hashes for their packages/ISO's nowadays.]
I've added these hashes to the README.md. Thanks for the suggestion!
Forgive me if I am missing something here, but, since a hash used to be published for the zip pack containing the compiled MS-Win executables and docs, in order to verify its integrity, I have looked around to find such a hash for the latest pack and no matter how hard I looked, I couldn't find any.
I had to resort to the next best thing: as I am most of the times using wget to download, I took the ETag from the server messages, that luckily -- as this is not always the case -- is the MD5 sum of this latest zip pack; it verifies OK, but, to me, this is just a rather ugly workaround.
Has any hash for the v4.4 MS-Win zip pack ever been published (and if yes, kindly somebody point me to it, otherwise, Jesse, kindly publish it).
It might have been deemed unnecessary, as the download comes through https, but, then, again, it has always been kind of reassuring to me to have a verification hash for the pack.
Here is the last portion of the MS-WinXP cmd stdout of my wget command (that is on top of the output), for reference:
In any case, many thanks for making publically available this wonderful suite of integrity checking applications!