On Tue, Mar 31, 2015 at 3:29 PM, Jurgen Schmurgen <[email protected]> wrote:
> When attempting to veify the ISO sig using GPA/Kleopatra, I get the > following message: > > tails-i386-1.3.1.iso.sig: Not enough information to check signature > validity. > Signed on 2015-03-22 18:15 with unknown certificate > 0xA5091F72C746BA6B163D1C183C83DCB52F699C56. > The validity of the signature cannot be verified. > > On your site, you say things are legit if I get the following: > > > Not enough information to check the signature validity. > Signed on ... by [email protected] (Key ID: 0x58ACD84F > The validity of the signature cannot be verified. > > > The seems to me to be a bit of a difference and I don't want to install > without checking with you. Perhaps I'm being a bit ignorant and you can set > me straight. > It is showing you the subkey fingerprint. I see the same message. They should update their documentation. gpg: Good signature from "Tails developers (offline long-term identity key) <[email protected]>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: A490 D0F4 D311 A415 3E2B B7CA DBB8 02B2 58AC D84F Subkey fingerprint: A509 1F72 C746 BA6B 163D 1C18 3C83 DCB5 2F69 9C56 I suggest you sign the Tails key to get rid of the warning once you have followed the instructions to verify it [1]. You wouldn't want to confuse that warning with the "Signature is invalid" warning which looks similar and actually means that the signature can't be found. After you trust the Tails key and you verify the ISO again you should see "Signature is valid" with a bright green background. Also Tails 1.3.2 was released today so you should use that instead of 1.3.1. [1]: https://tails.boum.org/doc/get/trusting_tails_signing_key/index.en.html
_______________________________________________ tails-support mailing list [email protected] https://mailman.boum.org/listinfo/tails-support To unsubscribe from this list, send an empty email to [email protected].
