Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 112042 - glibc corruption found by up2date download
glibc corruption found by up2date download
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Fanny Augustin
Depends On:
  Show dependency treegraph
Reported: 2003-12-13 11:07 EST by Gavin C. Flower
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-02 12:13:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
error dialog date/time etc. (236.70 KB, image/png)
2003-12-13 11:11 EST, Gavin C. Flower
no flags Details

  None (edit)
Description Gavin C. Flower 2003-12-13 11:07:48 EST
Description of problem:

Used up2date to download glibc and it failed:
[root@jupiter root]# up2date
SSL exception (104, 'Connection reset by peer')
SSL exception (-1, 'Unexpected EOF')
error: rpmts_HdrFromFdno: V3 DSA signature: BAD, key ID db42a60e
error: rpmts_HdrFromFdno: MD5 digest: BAD
Expected(820132f1fc2f6985ac13720333df6c27) !=
[root@jupiter root]#

Version-Release number of selected component (if applicable):

How reproducible:
every time

Steps to Reproduce:
1.rerun up3date
2.attempt to download glibc
Actual results:

Expected results:
update glibc

Additional info:
Comment 1 Gavin C. Flower 2003-12-13 11:11:46 EST
Created attachment 96511 [details]
error dialog date/time etc.
Comment 2 Adrian Likins 2004-09-02 12:13:59 EDT
Probably just a network  error while downloading. (ie,
haven't seen any other reports that match this, and
the packages the server has are valid). If this
is still occuring, please reopen this bug.

Note You need to log in before you can comment on or make changes to this bug.