GPG Signature not valid for glibc-2.3.2-104.4 on using Up2date after clean install.

[Bevan C. Bennett]

Mark Mcdonough wrote:
> Greetings everyone.
> 
> After a clean install of Fedora and running up2date I am getting the
> following message.
> 
> The package glibc-2.3.2-101.4 does not have a valid GPG signature.
> It has been tampered with or corrupted. Continue?
> 
> Of course I did not continue. Anyone can explain away this one?

You're probably using the main (sloooow and overloaded) repository 
instead of a mirror and ended up with a corrupted binary when up2date 
downloaded it. The GPG signature on my glibc-2.3.2-101.4 rpm looks fine.

Do yours look like this?
fedora-1-updates]> ls -l glibc-2.3.2-*
5147097 Jan 12 05:55 glibc-2.3.2-101.4.i686.rpm
3462096 Jan 12 05:55 glibc-2.3.2-101.4.i386.rpm

fedora-1-updates]> md5sum glibc-2.3.2-*
7eeb7de975cfc94a1cb42e9cbda946f6  glibc-2.3.2-101.4.i686.rpm
435668fdcb571bbb198f611c612343f4  glibc-2.3.2-101.4.i386.rpm

fedora-1-updates]> rpm -K glibc-2.3.2-101.4.*
glibc-2.3.2-101.4.i386.rpm: (sha1) dsa sha1 md5 gpg OK
glibc-2.3.2-101.4.i686.rpm: (sha1) dsa sha1 md5 gpg OK