Bad signature for updated packages

Leonard Chatagnier lenc5570 at sbcglobal.net
Thu Dec 10 01:45:50 UTC 2009


--- On Wed, 12/9/09, Jochen Antesberger <jochen-2009-4thquarter at ozark.de> wrote:

> From: Jochen Antesberger <jochen-2009-4thquarter at ozark.de>
> Subject: Re: Bad signature for updated packages
> To: ubuntu-users at lists.ubuntu.com
> Date: Wednesday, December 9, 2009, 5:03 PM
> Am Wed, 09 Dec 2009 12:15:01 -0600
> schrieb Leonard:
> 
> > Jochen Antesberger wrote:
> >> I just did my ususual aptitude update session to
> install security
> >> updates. Turns out that ntpdate updates fine, but
> the other three
> >> candidates, gdm, devicekit-disks and
> seahorse-plugins cause a warning
> >> that these packages are not trusted.
> >>
> >> Is there a problem on the Ubuntu servers (using
> the german mirror) or
> >> do I have a corrupted file transfer there?
> 
> > Usually when I get that notice using aptitude it ask
> me if I want to
> > install them or not.
> > I usually just click yes to install as I know what's
> in my source.list
> > file and intend to
> > install whatever is available.  I don;t use the
> German mirror but don't
> > think you have
> > a corrupted file or Ubuntu server issue.  Usually
> you just have to
> > accept the install to
> > get the apps installed on your system.
> 
> Yes, I could override the message. I do that with self
> build packages on 
> my Debian machines, because I'm too lazy to sign them. But
> with official 
> packages the whole point of the setup is to prevent a
> compromised mirror 
> to put malign packages on my system. So while I suppose
> there is an 
> explanation for this I didn't want to just go ahead.
> 
> Anyway, since I never really dived into internals it took
> me a bit to 
> find where apt keeps the files I suspected to be corrupt
> and so they were 
> indeed. Made a backup, deleted them and reran aptitude
> update. No more 
> complaints.
> 
> Cheers!
> 
Interesting, I've never seen that error for a corrupt file before.  Maybe because I use the cli and see error codes using aptitude but don't know.
How did you determine the files were corrupt? IYP,
Leonard Chatagnier
lenc5570 at sbcglobal.net





More information about the ubuntu-users mailing list