GPG error when pulling updates from security.debian.org
Did an aptitude update on a Debian Lenny box and got:
W: GPG error: http://security.debian.org lenny/updates Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AED4B06F473041FA
W: You may want to run apt-get update to correct these problems
According to Debian News, the GPG key expired:
This key rollover is a normal maintenance task and was started in August 2010. For security reasons Debian's archive signing keys regularly expire after three years.
Solution:
sudo aptitude install debian-archive-keyring
---8<---
The following packages will be upgraded:
debian-archive-keyring
1 packages upgraded, 0 newly installed, 0 to remove and 59 not upgraded.
---8<---
Unpacking replacement debian-archive-keyring ...
Setting up debian-archive-keyring (2010.08.28~lenny1) ...
gpg: key F42584E6: "Lenny Stable Release Key " not changed
gpg: key 55BE302B: "Debian Archive Automatic Signing Key (5.0/lenny) " not changed
gpg: key 6D849617: "Debian-Volatile Archive Automatic Signing Key (5.0/lenny)" not changed
gpg: key B98321F9: public key "Squeeze Stable Release Key " imported
gpg: key 473041FA: public key "Debian Archive Automatic Signing Key (6.0/squeeze) " imported
gpg: Total number processed: 5
gpg: imported: 2 (RSA: 2)
gpg: unchanged: 3
gpg: no ultimately trusted keys found
---8<---
Now the "NO_PUBKEY" error is gone and I can go one with installing my updates.
7 Comments
1. Fred replies at 4th April 2011, 3:53 pm :
Ok… wow. Finally problem solved!!
2. bervalk replies at 12th June 2011, 1:16 am :
Thanks…
3. Nabi replies at 18th July 2011, 11:23 am :
Thank you for your tips.
It was too useful for me.
4. Mikexad replies at 20th August 2011, 11:06 am :
Thanks!
5. ofonime replies at 15th March 2012, 4:30 am :
it didnt work same error msg
6. kelaslinux replies at 20th June 2012, 6:35 am :
its working! thanks
7. Lorenzo Marano replies at 23rd May 2013, 3:11 am :
Thanks.
Leave a comment