OP: You should put a checksum with a file like this. It would be an obvious ploy to replace some of the files with trojans. If the original is though to be clean, people may execute exploits contained in a zip they thought to be real.
I downloaded a copy from:
[http]://blog.magicaltux.net/wp-content/uploads/2014/03/MtGox2014Leak.zip
at in the morning PST (2014.03.09) and this is the checksum I get:
snip@snip ~> sha256 MtGox2014Leak.zip
SHA256 (MtGox2014Leak.zip) =
ffcf6742ab84d7e29ef16ca4f0829d7c4e7a4f739414d2b6d2ded52f05e75a67Several people on a different thread get the same checksum, but I don't know if they got it from the same place or not.
Checksums are easy to check, reliable, and quite critical for data such as this. I would be very wary of anything sensitive that I downloaded which did not come with a checksum, and I would (and do) cross-check these.
If anyone finds a file of the same name with a different checksum it would be good to report it (even worth starting a new thread) and handing it over to people who can analyze the contents. We really don't need any more people losing money to stupid things associated with Mt. Gox...though I suspect we'll see a lot more in the weeks to come