Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] md5 checksums not matching on some downloads

Thanks for fixing this up!


From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Denis Roy
Sent: Thursday, December 16, 2010 7:21 PM
To: cross-project-issues-dev@xxxxxxxxxxx
Subject: Re: [cross-project-issues-dev] md5 checksums not matching on some downloads


Our servers cache the checksums for optimal performance.  Checksums are queued for computation after the first ever download of any given file.  I have cleared them for this file, waited a bit, and they were recreated.  The retrieved checksums are now correct.

This means that, at some point, the file on disk was altered.

Is this a glitch?  I don't know.  In a security mindset, I can see how this can be a feature.  In my unqualified opinion, once a file is on it should never be altered, but instead replaced with a new version.


On 16/12/2010 7:17 PM, Konstantin Komissarchik wrote:

The build system we use for Sapphire verifies downloads of various dependencies by checking published md5 checksums. We’ve been having trouble today moving to Indigo M4 because for at least one of the files, download server is consistently reporting the wrong checksum.


This is the file in question:

Actual Checksum: 353f7c08746bcd6ab336c2ca9b3e7556


This is the how we fetch the checksum:

Retrieved Checksum: aca8645f904c11ee2ba4cfe84f5253c4


Curiously, if I go to EMF download site directly and hit their link for md5 checksum, I get the checksum that actually matches the downloaded file. Here is that URL:


This appears to be a case of a glitch in infrastructure. Yes? Can this be fixed?


- Konstantin

cross-project-issues-dev mailing list


Back to the top