Sorry, it took a while to find the right people to explain the network
configuration.
A BlueCoat was recently installed, which among other tasks is a proxy
server. The bluecoat is supposed to be an inline cache.
The error I cut and pasted the messages from today was roughly
2:45-3:00pm EST.
The server's IP is 128.150.140.174. I have been told that the
BlueCoat's IP should not show up in the access logs.
Given your response, will a solution like apt-proxy, approx, or
apt-cacher help me? Or will that only help me if I can have it's
requests to *.debian.org not be filtered?
Warren
-----Original Message-----
From: Florian Weimer [mailto:f...@deneb.enyo.de]
Sent: Friday, December 19, 2008 3:32 PM
To: Overholt, Warren
Cc: 509...@bugs.debian.org
Subject: Re: Bug#509221: security.debian.org: Repeated intermittant GPG
BADSIG errors with Automatic Signing Key
* Warren Overholt:
> For the past several months I have been getting periodic errors with
> the signing key as follows:
>
> sudo aptitude update
> ........
> W: GPG error: http://ftp.debian.org etch Release: The following
> signatures were
> invalid: BADSIG A70DAF536070D3A1 Debian Archive Automatic Signing Key
> (4.0/etch)
> <ftpmas...@debian.org>
> W: You may want to run apt-get update to correct these problems
Are you behind a proxy server? If the proxy ignores the cache bypass
requested by APT, such problems may indeed occur.
In order to debug this, we need the approximate time of the failure
(including the time zone) and the IP address you expect us to see.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
