-----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 debian-8-turnkey-ansible_14.2-1_amd64.tar.gz.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 debian-8-turnkey-ansible_14.2-1_amd64.tar.gz 5d9128bd3d74855aaeb1f4797bcbe1810b016ff600a140899a5162003891e347 debian-8-turnkey-ansible_14.2-1_amd64.tar.gz $ sha512sum debian-8-turnkey-ansible_14.2-1_amd64.tar.gz 36259c360f5c0b3935aa3f00f1d3be5aa7b70012f463fd210cbc9a742cc20d9384606fbb49924de139526c3c05aeb449df84bac63d3c3659d38d08ee6ceef01c debian-8-turnkey-ansible_14.2-1_amd64.tar.gz Note, you can compare hashes automatically:: $ sha256sum -c debian-8-turnkey-ansible_14.2-1_amd64.tar.gz.hash debian-8-turnkey-ansible_14.2-1_amd64.tar.gz: OK $ sha512sum -c debian-8-turnkey-ansible_14.2-1_amd64.tar.gz.hash debian-8-turnkey-ansible_14.2-1_amd64.tar.gz: OK -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJZiZeZAAoJEIXCXpWhbrlN/70H/j5viPXxbBFhjT5BfsG0sZVS rie83f+moK7bMCAT2qqHJIPBMwSMaTha3IvrQS1G9UG3+Ne+tUwbt23SQ3jSdO/N jez2rPc0VcBFqLLS5V0CS+juLfUoDM9+SDf4A2m8Ep8VAx3KhHD6PtajSRjuM0QG jBRtgAxHC08T4f7oVw+PjX/8J6u2T6B0SjaiEh0GXBG3sNUubM5FF5YyR2oDBMWM suPUKYPXpEIZZV737h9+0r4PkHo8RSekIJAGXCp0kW1JiJv5WiWZO8l+rSCfk6ih sv0DoyZhhe8GMBByAW79lkOakUmuWmV56CrGgjjHEiNpCfawuFc0kx4IOwIOKKk= =ZIIi -----END PGP SIGNATURE-----