On 7/6/05, Darryl Gregorash wrote:
david rankin wrote:
Mates,
I have dlded SUSE-9.3-Prof-i386-CD1.iso from 2 different mirrors. Each time the checksum is the same, but does *not* match the published checksum. Is this a known problem?
[david@bonza scripts]$ cat MD5SUMS 44959bbe1055f1c16bac1e2abcc2d270 SUSE-9.3-Prof-i386-CD1.iso ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 43f7c0f15e2f3abf2704986c01fdcf90 SUSE-9.3-Prof-i386-CD2.iso b41d051c8cc6d955f4755f039b19da03 SUSE-9.3-Prof-i386-CD3.iso 5519222959efb69184474c5934d33ec3 SUSE-9.3-Prof-i386-CD4.iso 488467804038d955a8f47735fa60aaff SUSE-9.3-Prof-i386-CD5.iso 04d2ebe4e0b8b00bc83cdc180a79e667 SUSE-9.3-Eval-DVD.iso
[david@bonza scripts]$ md5sum SUSE-9.3-Prof-i386-CD1.iso 0e7ab1893c357ee0954e951c8cf7bdb1 SUSE-9.3-Prof-i386-CD1.iso ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I got the CDs from USC last night, but didn't check the sums until this afternoon. CD1 gave the same md5sum as you report here. Assuming an ftp error, I downloaded the image file again, and the new file gave the same md5sum as stated in the sums file. However, this thread made me think the other, more likely, possibility.
I just checked the records for both of these ftp connections (I still have those console sessions open) , and see the following:
MD5SUMS was changed on July 1, but the CD1 image file remained at the June 27 version until after I completed my ftp session last night. Today, the image file has been updated, and shows a July 1 date. The file size has remained unchanged.
Are you saying that the original CD1 on the ftp server was wrong? And that those of us that downloaded a copy should do so again? Thanks, Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century