Re: Keys too old or compromised ?

[Hans <hans.ullrich@pop-h.niedersachsen.de>]

Am Mittwoch, 22. November 2006 09:53 schrieb Goswin von Brederlow:
> hans-u@t-online.de (Hans-J. Ullrich) writes:
> > Dear maintainers,
> >
> > I just get this message when using apt-get update.
> >
> > ---------- snip ----
> >
> > W: Es gibt keine öffentlichen Schlüssel für die folgenden Schlüssel-IDs:
> > A70DAF536070D3A1
> > W: Es gibt keine öffentlichen Schlüssel für die folgenden Schlüssel-IDs:
> > A70DAF536070D3A1
> > W: Es gibt keine öffentlichen Schlüssel für die folgenden Schlüssel-IDs:
> > A70DAF536070D3A1
> >
> > --------- snap ---------
> >
> > I suppose, the ziyi_key has ran out of time. Where do I get a new one ?
> >
> > Regards
> >
> > Hans
>
> First this is just a warning so don't worry.
>
> The new archive key for etch has been created and the Release file is
> now signed by both the old and new key. Apt-get warns that it can't
> check one of the signatures but the other still holds. The message
> from apt could be better.
>
> As of last night there is a new debian-archive-keyring package
> containing that key. so with todays update that warning should go
> away.
>
> MfG
>         Goswin

Hi Goswin,

that is exactly what thought. I knew, that thle lifetime of the keys is on its 
end in these days, but I just wanted to make sure, I update the correct keys 
and to make sure, the keys are really outdated. Now we all know !

Thanks for the support !


Best regards

Hans