31 Mar
2010
31 Mar
'10
1:28 a.m.
Hi all,
I seem to have started getting this error in the last 24 hours:
W: GPG error: http://apt-cacher.lon.bitfolk.com lenny/volatile Release:
The following signatures were invalid: KEYEXPIRED 1269969909 KEYEXPIRED
1269969909 KEYEXPIRED 1269969909
W: You may want to run apt-get update to correct these problems
apt-get update doesn't fix it, and the obvious google seemed only to
suggest clock syncronisation problems (the clock appears to be correct).
Any insight appreciated :)
Thanks
Joseph
31 Mar
31 Mar
7:23 a.m.
On 31/03/2010 02:28, Joseph Heenan wrote:
Hi all,
I seem to have started getting this error in the last 24 hours:
W: GPG error: http://apt-cacher.lon.bitfolk.com lenny/volatile Release:
The following signatures were invalid: KEYEXPIRED 1269969909 KEYEXPIRED
1269969909 KEYEXPIRED 1269969909
W: You may want to run apt-get update to correct these problems
apt-get update doesn't fix it, and the obvious google seemed only to
suggest clock syncronisation problems (the clock appears to be correct).
Any insight appreciated :)
The current unix time is 1270023712 so it has rightly expired.
I don't know debian enough to know whether it is teh caches key or the
upstream key that has expired, but you could try waiting a bit and
trying again.
--
Dee Earley (dee(a)earlsoft.co.uk)
irc: irc://irc.blitzed.org/
web: http://www.earlsoft.co.uk
phone: +44 (0)780 8369596
9:23 a.m.
Hi Joseph,
On Wed, Mar 31, 2010 at 10:28:01AM +0900, Joseph Heenan wrote:
I seem to have started getting this error in the last
24 hours:
W: GPG error: http://apt-cacher.lon.bitfolk.com lenny/volatile Release:
The following signatures were invalid: KEYEXPIRED 1269969909 KEYEXPIRED
1269969909 KEYEXPIRED 1269969909
W: You may want to run apt-get update to correct these problems
$ wget -qO - http://www.debian.org/volatile/lenny-volatile.asc | gpg --import -
gpg: key 6D849617: public key "Debian-Volatile Archive Automatic
Signing Key (5.0/lenny)" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
$ gpg --list-keys 6D849617
pub 2048R/6D849617 2009-01-24 [expires: 2013-01-23]
uid Debian-Volatile Archive Automatic Signing Key (5.0/lenny)
Looks like they generated a new key.
$ sudo apt-key list
/etc/apt/trusted.gpg
--------------------
pub 1024D/6070D3A1 2006-11-20 [expired: 2009-07-01]
uid Debian Archive Automatic Signing Key (4.0/etch)
<ftpmaster(a)debian.org>
pub 1024D/ADB11277 2006-09-17
uid Etch Stable Release Key <debian-release(a)lists.debian.org>
pub 1024D/BBE55AB3 2007-03-31 [expired: 2010-03-30]
uid Debian-Volatile Archive Automatic Signing Key (4.0/etch)
pub 1024D/16BA136C 2005-08-21
uid Backports.org Archive Key <ftp-master(a)backports.org>
sub 2048g/5B82CECE 2005-08-21
pub 1024D/F42584E6 2008-04-06 [expires: 2012-05-15]
uid Lenny Stable Release Key <debian-release(a)lists.debian.org>
pub 4096R/55BE302B 2009-01-27 [expires: 2012-12-31]
uid Debian Archive Automatic Signing Key (5.0/lenny)
<ftpmaster(a)debian.org>
pub 2048R/6D849617 2009-01-24 [expires: 2013-01-23]
uid Debian-Volatile Archive Automatic Signing Key (5.0/lenny)
I guess you were still using the etch one (BBE55AB3).
I expect:
$ wget -qO - http://www.debian.org/volatile/lenny-volatile.asc | sudo apt-key add -
will fix it.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
You dont have to be illiterate to use the Internet, but it help's.
-- Mike Bristow
1 Apr
1 Apr
6:17 a.m.
Hi Andy,
On 3/31/2010 6:23 PM, Andy Smith wrote:
On Wed, Mar 31, 2010 at 10:28:01AM +0900, Joseph
Heenan wrote:
Thanks for the thoughts. I do definitely have this new key in the apt
key list now, but still get the problem.
http://forum.nginx.org/read.php?31,69929,69929 suggests the uk archives
are still being signed with the old key and/or are out of date.
I've tried to switch my sources.list to volatile.debian.org, but it
seems my VPS tries to contact this over ipv6 and fails to connect. (I've
not deliberately enabled ipv6 on my VPS, but it seems to be getting an
ipv6 address from somewhere...)
Joseph
I seem to have started getting this error in the
last 24 hours:
W: GPG error: http://apt-cacher.lon.bitfolk.com lenny/volatile Release:
The following signatures were invalid: KEYEXPIRED 1269969909 KEYEXPIRED
1269969909 KEYEXPIRED 1269969909
W: You may want to run apt-get update to correct these problems
$ wget -qO - http://www.debian.org/volatile/lenny-volatile.asc | gpg --import -
gpg: key 6D849617: public key "Debian-Volatile Archive Automatic
Signing Key (5.0/lenny)" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
$ gpg --list-keys 6D849617
pub 2048R/6D849617 2009-01-24 [expires: 2013-01-23]
uid Debian-Volatile Archive Automatic Signing Key (5.0/lenny)
Looks like they generated a new key.
2:38 p.m.
Hi Joseph,
On Thu, Apr 01, 2010 at 03:17:03PM +0900, Joseph Heenan wrote:
Thanks for the thoughts. I do definitely have this new
key in the apt key
list now, but still get the problem.
Me too. I guess they haven't re-signed the files with the new key
yet.
I've tried to switch my sources.list to
volatile.debian.org, but it seems
my VPS tries to contact this over ipv6 and fails to connect. (I've not
deliberately enabled ipv6 on my VPS, but it seems to be getting an ipv6
address from somewhere...)
Okay. Do you want to fix your IPv6, disable IPv6 or make your system
prefer IPv4 addresses?
If you want to fix IPv6, it might be a little involved. Please start
by showing the output of "ip -6 addr" and "ip -6 ro". Bear in mind
that once it's fixed you should then investigate ip6tables for IPv6
firewalling.
Disabling IPv6 can't be done without a reboot. Google for "blacklist
ipv6 debian" and you'll see how.
Applications that use getaddrinfo instead of gethostbyname should
pay attention to /etc/gai.conf for address selection. If you open
that file you'll see this part:
51 #
52 # For sites which prefer IPv4 connections change the last line to
53 #
54 #precedence ::ffff:0:0/96 100
I think if you uncomment that then apt-get and aptitude should
prefer IPv4 addresses.
It would be nice if apt had a config option for preferring one or te
other as many applications do, but I can't see one.
Personally I will just be waiting a few more days to see if they fix
it.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
18 Apr
18 Apr
8:49 a.m.
Hi Andy,
Thanks for the advice on this.
Andy Smith wrote:
Thanks; I've gone for the "disable" option for now as that appears not
to have a disadvantage and I like to keep things simple. :-)
Joseph
On Thu, Apr 01, 2010 at 03:17:03PM +0900, Joseph
Heenan wrote:
Seems like it is fixed now.
Thanks for the thoughts. I do definitely have
this new key in the apt key
list now, but still get the problem.
Me too. I guess they haven't re-signed the files with the new key
yet. I've tried
to switch my sources.list to volatile.debian.org, but it seems
my VPS tries to contact this over ipv6 and fails to connect. (I've not
deliberately enabled ipv6 on my VPS, but it seems to be getting an ipv6
address from somewhere...)
Okay. Do you want to fix your IPv6, disable IPv6 or make your system
prefer IPv4 addresses?
If you want to fix IPv6, it might be a little involved. Please start
by showing the output of "ip -6 addr" and "ip -6 ro". Bear in mind
that once it's fixed you should then investigate ip6tables for IPv6
firewalling.
Disabling IPv6 can't be done without a reboot. Google for "blacklist
ipv6 debian" and you'll see how.
5214
days inactive
5232
days old
5 comments
3 participants
participants (3)
-
Andy Smith -
Dee Earley -
Joseph Heenan