By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
464,806 Members | 1,337 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 464,806 IT Pros & Developers. It's quick & easy.

wrong md5 checksum

P: n/a
Hi,

the download page (http://www.python.org/download/releases/3.0/) for
Python 3000 shows :

9119625244b17aa35ed94b655a2b2135 13491200 python-3.0b1.msi

but I got

9119625244a57aa35ed94b655a2b2135 13491200 python-3.0b1.msi

(44a57 rather than 44b17 )

with several md5 checkers ( MdChecker (http://getmd5checker.com/) or a C
prog I've written)

what's wrong ?
Jul 1 '08 #1
Share this Question
Share on Google+
4 Replies

P: n/a
kkwweett a écrit :
Hi,

the download page (http://www.python.org/download/releases/3.0/) for
Python 3000 shows :

9119625244b17aa35ed94b655a2b2135 13491200 python-3.0b1.msi

but I got

9119625244a57aa35ed94b655a2b2135 13491200 python-3.0b1.msi

(44a57 rather than 44b17 )

with several md5 checkers ( MdChecker (http://getmd5checker.com/) or a C
prog I've written)
Wrong md5 checksum even with Python2.5 :
import md5
m=md5.new()
message=open("python-3.0b1.msi","rb").read()
m.update(message)
m.hexdigest()

Answer : '9119625244a57aa35ed94b655a2b2135'
Does anyone know what can be done to decide wether the file is corrupted
or the checksum given is wrong ?
Jul 1 '08 #2

P: n/a
On Tue, 01 Jul 2008 17:54:05 +0200, kkwweett <kk******@hotmail.frwrote:
kkwweett a écrit :
>Hi,

the download page (http://www.python.org/download/releases/3.0/) for
Python 3000 shows :

9119625244b17aa35ed94b655a2b2135 13491200 python-3.0b1.msi

but I got

9119625244a57aa35ed94b655a2b2135 13491200 python-3.0b1.msi

(44a57 rather than 44b17 )
[snip]
Does anyone know what can be done to decide wether the file is corrupted
or the checksum given is wrong ?
For what it's worth, md5sum (GNU coreutils) 5.93 agrees with
your result.

This interesting almost-agreement could result from

A. an error in the software that computed the value for the web page,
B. a transcription error in putting the checksum on the web page,
C. accidental corruption of the file, or
D. a deliberate attempt to substitute a file with a similar MD5 sum.

Possibility C is unlikely, but would be the most exciting
development in cryptology this year. If C turns out to be the
explanation, I hope someone will make sure sci.crypt gets told.
Possibility D would be awfully interesting, too.

--
To email me, substitute nowhere->spamcop, invalid->net.
Jul 1 '08 #3

P: n/a
>
A. an error in the software that computed the value for the web page,
B. a transcription error in putting the checksum on the web page,
C. accidental corruption of the file, or
D. a deliberate attempt to substitute a file with a similar MD5 sum.
It seems that the answer is probably B. But, according to the release
website manager, a mystery remains :

http://mail.python.org/pipermail/pyt...ly/014281.html
Jul 2 '08 #4

P: n/a


kkwweett wrote:
>
>>
A. an error in the software that computed the value for the web page,
B. a transcription error in putting the checksum on the web page,
C. accidental corruption of the file, or
D. a deliberate attempt to substitute a file with a similar MD5 sum.

It seems that the answer is probably B. But, according to the release
website manager, a mystery remains :

http://mail.python.org/pipermail/pyt...ly/014281.html
Marcin Kowalczyk pointed out in a follow-up to the above that the
replacement of 'a5' with 'b1' could have been part of a global
search/replace that would have been correct everywhere else on the page.
Thus case C. Barry remembers doing some such.

Lesson. Take care with blind global replacements.

Jul 3 '08 #5

This discussion thread is closed

Replies have been disabled for this discussion.