msi installation file that I downloaded has the correct SHA-256 hash code, but I think I should be able to verify the signature of the installation file in order to have complete assurance that the file hasn’t somehow been tampered with. It would appear that I have the correct public key/certificate for Crytomator installed in Kleopatra and the Cryptomator. I checked the SHA-256 hash of the Cryptomator-1.6.5-圆4.msi installation file using Karenware’s Hasher tool and the SHA-256 code generated by Hasher matches the SHA-256 hash code shown on the Cryptomator download page for the Cryptomator-1.6.5-圆4.msi installation file. I checked the fingerprint of the Cryptomator public key certificate in Kleopatra (using Properties of the Cryptomator public certificate) and the fingerprint matches the fingerprint shown on the download page for the public key/certificate. msi installation file using the new public certificate that I created from the signature text shown on the download page, I changed the signature file extension name from “.asc” to “.sig”, but this didn’t work either. When Kleopatra failed to verify/decrypt the. When I created a new public key file on my computer by copying and pasting the public key text (shown on the download page) into a text file and naming it as “Cryptomator-1.6.5-圆4.msi.asc”, and I tried to import it as the Cryptomator public certificate into Kleopatra, Kleopatra didn’t seem to import it (presumably because Kleopatra already had the public key installed). I believe I already had the latest Cryptomator public key imported into Kleopatra (along with an expired key) when I first tried to verify/decrypt the version 1.6.5 installation. out file stroked out with a horizontal line through the middle of the file name)
I downloaded the installation file “Cryptomator-1.6.5-圆4.msi” and its PGP signature file “Cryptomator_1.6.5-圆4.msi.asc” and tried to verify/decrypt the PGP signature in Gpg4Win’s Kleopatra (latest version installed using Gpg4win, 3.1.16), but the verification/decryption fails with the error messages
0 kommentar(er)
