How to check MD5SUM.gpg and the the iso

[kubuntux]

Im am trying to check the MD5SUM.gpg

ubuntu@ubuntu:~/Desktop$ gpg --verify MD5SUMS.gpg MD5SUMS
gpg: Signature made Thu 19 Apr 2007 08:58:35 AM CEST using DSA key ID FBB 75451
gpg: Can't check signature: public key not found

------

The surprise think is that key FBB75451 I found in adept_manager under
autentication ... put gpg not ...

Any suggestion ? I am triing to follow this:

https://help.ubuntu.com/community/VerifyIsoHowto

but :

ubuntu@ubuntu:~/Desktop$ gpg --recv-keys 0xFBB75451
gpg: no keyserver known (use option --keyserver)
gpg: keyserver receive failed: bad URI

Please where is the official key and how to check it ?

[penguin.ch]

Re: How to check MD5SUM.gpg and the the iso

gpg --recv-keys 0xFBB75451

How about gpg --keyserver pgp.mit.edu --recv-keys 0xFBB75451 instead?

[kubuntux]

Re: How to check MD5SUM.gpg and the the iso

Thanks you very much ... this does work! I think I would be very better to download the public key from mit.edu instead of searching the key on cd

[kubuntux]

Re: How to check MD5SUM.gpg and the the iso

But why there is no ubuntu public downloadable from the ubuntu download page or from ubuntuhashes ? I discover the key id only by the tutorial ... why does not report it on download ?

[kubuntux]

Re: How to check MD5SUM.gpg and the the iso

For example I have tried this:

(starting from an empty keyring)

gpg --keyserver pgp.mit.edu --recv-keys 0xFBB75451

then

gpg -a --export

(removing the preceding key)

gpg --keyserver subkeys.pgp.net --recv-keys 0xFBB75451

gpg -a --export

and the both export ARE NOT THE SAME

But both will say that the same result:

gpg: Signature made Thu 19 Apr 2007 08:58:35 AM CEST using DSA key ID FBB
75451
gpg: Good signature from "Ubuntu CD Image Automatic Signing Key <cdimage@
ubuntu.com>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the ow
ner.
Primary key fingerprint: C598 6B4F 1257 FFA8 6632 CBA7 4618 1433 FBB7 5451

Maybe the both keyservers contains multiple public keys ... under the same ID
and maybe it share the same "cdimage" keys


Who can explain me this ?