I am doing this comparison every time new version comes. And yes, I would like to create a script for secure download. As integrity is a serious business, I believe that there shouldn't be any alterations.
Well, it would be better not to change anything because this modification prevents automatic check from command line. My workflow is to put EBF94159 EA157C78 9A810022 14A4EB43 6C99C0BC 4484E8B4 244831B2 in notepad++, than delete all spaces, convert case to lowercase, than I paste string from command line bellow and then select one of them. If the other string is the same it will be highlighted as well. I think this is not necessary, just brings confusion.
Hi, can you please explain to me why there are difference in case and spaces regarding sha256 checksum? For example, I have downloaded the zip, sha256sum reports: sha256sum KeePass-2.40.zip ebf94159ea157c789a81002214a4eb436c99c0bc4484e8b4244831b237391357 KeePass-2.40.zip but on your web page there is a different (considering case and spaces) string. KeePass-2.40.zip: SHA-256: EBF94159 EA157C78 9A810022 14A4EB43 6C99C0BC 4484E8B4 244831B2 37391357 Why there is a difference? Regards
WD Green 4 TB