-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 To ensure the image has not been corrupted in transmit or tampered with, perform the following two steps to cryptographically verify image integrity: 1. Verify the authenticity of this file by checking that it is signed with our GPG release key: $ curl https://keybase.io/turnkeylinux/pgp_keys.asc | gpg --import $ gpg --list-keys --with-fingerprint release@turnkeylinux.com pub 2048R/A16EB94D 2008-08-15 [expires: 2023-08-12] Key fingerprint = 694C FF26 795A 29BA E07B 4EB5 85C2 5E95 A16E B94D uid Turnkey Linux Release Key $ gpg --verify turnkey-postgresql-14.2-jessie-amd64-vmdk.zip.hash gpg: Signature made using RSA key ID A16EB94D gpg: Good signature from "Turnkey Linux Release Key " For extra credit you can validate the key's authenticity at: https://keybase.io/turnkeylinux 2. Recalculate the image hash and make sure it matches your choice of hash below. $ sha256sum turnkey-postgresql-14.2-jessie-amd64-vmdk.zip f5fa8651325e8a6afd51450a31c5852752f412c6bee8457b5a5a2fb86dadb6a5 turnkey-postgresql-14.2-jessie-amd64-vmdk.zip $ sha512sum turnkey-postgresql-14.2-jessie-amd64-vmdk.zip 1dd421157ad099145fdb2b271eda6fd7873ddec20e22dde8d496052f450fef0f2047a6ed2fb2e6fa10ebd83734795e15ce5964fcc55f5d06902b50a2400bae27 turnkey-postgresql-14.2-jessie-amd64-vmdk.zip Note, you can compare hashes automatically:: $ sha256sum -c turnkey-postgresql-14.2-jessie-amd64-vmdk.zip.hash turnkey-postgresql-14.2-jessie-amd64-vmdk.zip: OK $ sha512sum -c turnkey-postgresql-14.2-jessie-amd64-vmdk.zip.hash turnkey-postgresql-14.2-jessie-amd64-vmdk.zip: OK -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJZNo92AAoJEIXCXpWhbrlN6NYH/jOlBMx1Do3Hwi1qc+lJ5HGQ FBjz5btE45zvxEwuY2+QvuvRWDOtau15s7kvUkIJpmUCFPo6ZJjE2S8YwOBBxLzM n29LW5U3vwClkkul854mah124hKM20xHq++N5KH7LiN8QBHkbnu9X7hi2Qj3VjZ+ JAQ1JUg2jEz/F2xDBhKg2zwjNIhyZ+4AJaQA0Rm/wcolR0dekXhjhf1uFLw1azk8 eccVWKDTLFaCEUSf0h/kp8p/YWPAiMUcpbfYqmqcIBnb5kfMvduotSYtAIzCKg7+ 9/yYWMz/LAR1gEXVcvfjESRJGYpnQVVVXcSSSSdmW55r7kZ9Gq9Qfqex25mQb3k= =FHWC -----END PGP SIGNATURE-----