Lately, my Debian servers have been bugging me with stuff like this everytime I tried to apt-get update:
W: There are no public key available for the following key IDs:
W: You may want to run apt-get update to correct these problems</p>
and it tells you to ap-get update to solve the problem, which is of little help, since that is what caused the problem in the first place!
Here's the solution:
Don't forget to replace XYZ123 with the actual missing key.
No! Please at first make sure you have the recent version of debian-archive-keyring installed (some addittional repositories have similar packages).
And before adding random keys by hand, please make sure, that the fingerprint of the key you received matches the one the distributor hopefully has shown to you in a secure manor. You can see the fingerprint of a key with “gpg –fingerprint XYZ123″
Also please don’t run “apt-key add /root/.gnupg/pubring.gpg” since this will not only add the key you just downloaded, but every other key available in that specific keyring, too.
Better use “gpg –armor –export XYZ123 | apt-key add -” which will only add the one single key to the trusted keys of apt.
Would “apt-get install debian-archive-keyring” not do the trick?
apt-get install debian-archive-keyring was telling me I was installing from an untrusted source.
Here’s what I do now:
gpg –keyserver wwwkeys.eu.pgp.net –recv 9AA38DCD55BE302B
gpg –export –armor 9AA38DCD55BE302B | apt-key add -
You can also use:
apt-key adv –keyserver hkp://subkeys.pgp.net –recv-keys 9AA38DCD55BE302B