Bad MD5 of install42.iso

2007-11-01 Thread Przemysław Pawełczyk
Hi,

I dloaded the file from two different servers.
Here's what I got running md5sum:

1) MD5s for downloaded files
md5sum install42.iso
03dc43a1d18d3003843a1f13b3861917  install42.iso

Just for checking:
md5sum cd42.iso
7d4ba197d25088a4ad487f2830028c8d  cd42.iso

2) The numbers from MD5 official file:
MD5 (install42.iso) = b3a80c9010716ebc997571a1609cf334

Just for checking:
MD5 (cd42.iso) = 7d4ba197d25088a4ad487f2830028c8d

What should I do? To burn it or not to burn?

Regards,
pp

--
Przemys3aw Pawe3czyk (P2O2) - [EMAIL PROTECTED]
WWW: http://pp.kv.net.pl/ Forum: http://www.p2o2.fora.pl/

[demime 1.01d removed an attachment of type application/pgp-signature]



Re: Bad MD5 of install42.iso

2007-11-01 Thread ropers
On 01/11/2007, Przemys3aw Pawe3czyk [EMAIL PROTECTED] wrote:
 Hi,

 I dloaded the file from two different servers.
 Here's what I got running md5sum:

 1) MD5s for downloaded files
 md5sum install42.iso
 03dc43a1d18d3003843a1f13b3861917  install42.iso

 Just for checking:
 md5sum cd42.iso
 7d4ba197d25088a4ad487f2830028c8d  cd42.iso

 2) The numbers from MD5 official file:
 MD5 (install42.iso) = b3a80c9010716ebc997571a1609cf334

 Just for checking:
 MD5 (cd42.iso) = 7d4ba197d25088a4ad487f2830028c8d

 What should I do? To burn it or not to burn?

Could you specify exactly which server you have the bad iso from?

If you re-download the iso from the same server, is the md5 still bad?

It goes w/o saying that one shouldn't burn isos where the md5 already
red flags the file.



Re: Bad MD5 of install42.iso

2007-11-01 Thread Todd C. Miller
In message [EMAIL PROTECTED]
so spake =?ISO-8859-2?B?UHJ6ZW15c7NhdyBQYXdls2N6eWs=?= (pp):

 1) MD5s for downloaded files
 md5sum install42.iso
 03dc43a1d18d3003843a1f13b3861917  install42.iso

03dc43a1d18d3003843a1f13b3861917 is correct.  The MD5 file has been
updated but will take some time to propagate to the mirrors.

 - todd



Re: Bad MD5 of install42.iso

2007-11-01 Thread Constantine A. Murenin
On 01/11/2007, Przemys3aw Pawe3czyk [EMAIL PROTECTED] wrote:
 Hi,

 I dloaded the file from two different servers.
 Here's what I got running md5sum:

 1) MD5s for downloaded files
 md5sum install42.iso
 03dc43a1d18d3003843a1f13b3861917  install42.iso

 Just for checking:
 md5sum cd42.iso
 7d4ba197d25088a4ad487f2830028c8d  cd42.iso

 2) The numbers from MD5 official file:
 MD5 (install42.iso) = b3a80c9010716ebc997571a1609cf334

 Just for checking:
 MD5 (cd42.iso) = 7d4ba197d25088a4ad487f2830028c8d

 What should I do? To burn it or not to burn?

Yes, 03dc43a1d18d3003843a1f13b3861917 is the correct md5 for i386/install42.iso.

http://marc.info/?l=openbsd-wwwm=119391863124282w=2

Best regards,
Constantine.



Re: Bad MD5 of install42.iso

2007-11-01 Thread Richard Wilson

Todd C. Miller wrote:

In message [EMAIL PROTECTED]
so spake =?ISO-8859-2?B?UHJ6ZW15c7NhdyBQYXdls2N6eWs=?= (pp):

  

1) MD5s for downloaded files
md5sum install42.iso
03dc43a1d18d3003843a1f13b3861917  install42.iso



03dc43a1d18d3003843a1f13b3861917 is correct.  The MD5 file has been
updated but will take some time to propagate to the mirrors.

 - todd

  
I have also noticed that the MD5 files (at least for i386 and amd64) on 
spargel.kd85.com do not contain hashes for the x*42.tgz files. I expect 
this is a related issue?


Si1entDave



Re: Bad MD5 of install42.iso

2007-11-01 Thread Douglas A. Tutty
On Thu, Nov 01, 2007 at 02:58:42PM +0100, Przemys?aw Pawe?czyk wrote:
 
 I dloaded the file from two different servers.
 Here's what I got running md5sum:
 
 1) MD5s for downloaded files
 md5sum install42.iso
 03dc43a1d18d3003843a1f13b3861917  install42.iso
 
 Just for checking:
 md5sum cd42.iso
 7d4ba197d25088a4ad487f2830028c8d  cd42.iso
 
 2) The numbers from MD5 official file:
 MD5 (install42.iso) = b3a80c9010716ebc997571a1609cf334
 
 Just for checking:
 MD5 (cd42.iso) = 7d4ba197d25088a4ad487f2830028c8d
 
 What should I do? To burn it or not to burn?

To clarify, the md5sum on the files you downloaded from two different
servers were identical with each other (eliminating download problem)
but different from what is stated in the MD5 file.

If this is not true and each download produced a different MD5, try
using rsync to an rsync server to fix the iso file you downloaded.

Doug.