The following signatures were invalid

nospam@example.com (Marc 'Zugschlus' Haber) — Sat, 11 Aug 2007 06:26:09 +0000

My systems run cron-apt with an hourly rhythm, running off ftp2.de.d.o. Once in a while, some of them complain about invalid signatures on release files:

CRON-APT LINE: /usr/bin/apt-get update -o quiet=2
W: GPG error: http://debian.debian.zugschlus.de lenny Release: The following signatures were invalid: BADSIG A70DAF536070D3A1 Debian Archive Automatic Signing Key (4.0/etch) 
W: GPG error: http://debian.debian.zugschlus.de sid Release: The following signatures were invalid: BADSIG A70DAF536070D3A1 Debian Archive Automatic Signing Key (4.0/etch) 
W: You may want to run apt-get update to correct these problems

This usually happens in the late evening CEST. In the next cron-apt run, things are fine again. What's going on here? Is this part of a mirror update process where the Release and Release.gpg files are inconsistent?

Any idea how to get rid of these error messages?

DPotW: cron-apt

nospam@example.com () — Sun, 15 May 2005 09:57:00 +0000

Die dieswöchige Debian-Package of the Week ist cron-apt, ein Tool, mit dessen Hilfe unter anderem das automatische Ausrollen von Security-Updates auf eine große Zahl von Systemen drastisch vereinfacht wird.

Continue reading "DPotW: cron-apt"

Zugschlusbeobachtungen (Entries tagged as cron-apt)

The following signatures were invalid

DPotW: cron-apt