Eve Online Static Data Dump incorrect Checksums

Communications Center General Discussion
1

Not sure where to place this as there is no corresponding forum, so i thought best to place it in general. This out of the way…

I have downloaded the Static Data Dump and been hashing the ‘sde.zip’ file and checking it against the checksum md5 hash in the ‘checksums’ file. Here is a snippet from the ‘checksum’ file listed for download at the official resource:

“1c80fa2f50f17231f96030160611c894 sde.zip”

However, the checksum from PowerShells ‘Get-FileHash -Algorithm MD5 -Path ’ is returning ‘ED88DB6F375315BD421A7E5595EEDDD6’, in the application i’m developing the md5 hash library also produces the same ‘ed88db6f375315bd421a7e5595eeddd6’.

I have ran both multiple times and re-downloaded the ‘sde.zip’ file multiple times and it always produces the ‘ed88db6f375315bd421a7e5595eeddd6’ md5 hash and not the md5 hash specified in the ‘checksum’ file ‘1c80fa2f50f17231f96030160611c894’.

At this point i cannot confirm the issue. Despite all my downloading and testing, the md5 hash value in the ‘checksum’ file appears incorrect. Can you please confirm the problem and if possible please fix it, or give me the steps to fix it?

2

Using certutil -hashfile on sde.zip with MD5 produced ed88db6f375315bd421a7e5595eeddd6 for me as well, so you can rule out local modification.

3

Thank you for this update. It would appear the issue most likely is down to the ‘checksum’ file not being updated their end correctly. Again thank you for the update and i hope a GM or Support sees this :slight_smile:

1 Like
4

In case anyone is following this thread. I’ve contact Eve Online support directly about it, i hope to hear back later this week as it’s only Monday. My goal is to have the issue resolve promptly. The next update will be the resolution to the issue.

Thanks
Fluffy

5

Quick update incase anyone encounters this issue. Everything remains on-going, I’m still in contact with the GM’s and hope this is resolved shortly.

Thanks

6

Bump as this issue remains ongoing, over 1 month later