-----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-ansible-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-ansible-14.2-jessie-amd64-vmdk.zip 725de4cef8b81e0b0453f2308b47f1e88efee6931b5ab49132daf2b6052b38c5 turnkey-ansible-14.2-jessie-amd64-vmdk.zip $ sha512sum turnkey-ansible-14.2-jessie-amd64-vmdk.zip 74c7f05c9f9dd645a6d5da6cff4f99f97b7e3e29faf7d197268d84078a20e7f54b26314e0dda6992d5df8cd230b5fd88ec82f5d524305ba5775163576d6c5e75 turnkey-ansible-14.2-jessie-amd64-vmdk.zip Note, you can compare hashes automatically:: $ sha256sum -c turnkey-ansible-14.2-jessie-amd64-vmdk.zip.hash turnkey-ansible-14.2-jessie-amd64-vmdk.zip: OK $ sha512sum -c turnkey-ansible-14.2-jessie-amd64-vmdk.zip.hash turnkey-ansible-14.2-jessie-amd64-vmdk.zip: OK -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJZiZekAAoJEIXCXpWhbrlNc/YH+QFeEXPQau7nXHPo1rGhiOo5 zstRxHEqqRarrwdDKGJlPB3kvgYAhVMc6PvRqwqm5w+z/1DPi1fWYu4/fzsrUd+J j/eK8xexgkdA5AgLK+3FqULiIJxH9QHu3EgZZlBOdCOYo4l7Vypo6xT0d9iwkUvW 5LP+hBFImc/411Bg6l3Q6Re+wkqjYVEJlNlL7UTAuj2s4CsHde0Jt+DrOnTh7P+5 6fcMybvdZQtfaT8cQnEHY1gk28v+mGQPJJEDKI4DDAqSnKFhTLhfb33xmFeR4M9i uRfL1zbYitv5hsfW284lR4XzT/shka9Sdx9ELOX+wm2RihDZFseCo0OB5Lf9DMc= =Ekll -----END PGP SIGNATURE-----