-----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-owncloud-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-owncloud-14.2-jessie-amd64-vmdk.zip bbd9a60cee6cd23c69df8f79e53a7810723af127d3fa64717a06afc2f36550d9 turnkey-owncloud-14.2-jessie-amd64-vmdk.zip $ sha512sum turnkey-owncloud-14.2-jessie-amd64-vmdk.zip dfda04b383d1112ce66d21161e3e85b6ccaa37aafd4560c8a1ebf66cf1980fd05b6b0e822ff7200974cd77ab795fe5df707e0e18e6f1bc08c487ee51f3ce95d4 turnkey-owncloud-14.2-jessie-amd64-vmdk.zip Note, you can compare hashes automatically:: $ sha256sum -c turnkey-owncloud-14.2-jessie-amd64-vmdk.zip.hash turnkey-owncloud-14.2-jessie-amd64-vmdk.zip: OK $ sha512sum -c turnkey-owncloud-14.2-jessie-amd64-vmdk.zip.hash turnkey-owncloud-14.2-jessie-amd64-vmdk.zip: OK -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJZfb15AAoJEIXCXpWhbrlNKVUH/jWb2OS1igwv5Khzrv2NGjhW eaTyQ/wZbXOL06f0xrGCKPTPrkAaFJZKVCZISzyu2Leau0EFg+nlh3aL2eYfd8Ds X7NMnYLV/sBWVKmS6S0QNxaeDjnynD4whM4nY3jC8Ws9jgqH/VT/C5o0sHVgt6u3 M14BvDD6+pNFdOTnChtGAgywsQBNNtahOW6aNiDCWuQPo6KY0vnThJ3Qwkvzg6z/ VSNpl01OZmZq+jJLoPeTOj2g0TlmU6/rlisWRXic2rGK0RLVUE3rpbUTun06dZdE sTm+nZvIpaROCvO+DLXvIbi+YsHrf8MhQzmst8cuUjpc8wZXx1eOz5BKXqPUZqo= =5hIG -----END PGP SIGNATURE-----