Re: Community help needed to verify checksums for past releases

Thanks Markus for suggesting certUtil for Windows - the checksums
matched for the example you gave too, thank you.

Another contributor pointed out that archive.org actually does
record binary files, and I was able to download almost all of the
past releases from them and compare them to the files from the
old web server - and everything matched.

https://github.com/biopython/DIST/commit/d5f7b010e345eaf27e6a09d2dc22374098127ba7

We're still missing independent verification of just a handful of files:

biopython-1.30.win32-py2.2.exe
biopython-1.30.win32-py2.3.exe
biopython-1.30.win32-py2.4.exe
biopython-1.62.win32-py2.5.exe
biopython-1.62.win32-py2.6.exe
biopython-1.62.win32-py2.7.exe
biopython-1.62.win32-py3.3.exe
biopython-1.63b.win32-py2.6.exe
biopython-1.63b.win32-py2.7.exe
biopython-1.63b.win32-py3.3.exe
biopython-Mac.sit

Peter

On Wed, May 18, 2016 at 1:45 PM, Markus Piotrowski
<[email protected]> wrote:
> A Windows built-in tool is certUtil:
>
> certUtil -hashfile pathToFileToCheck [HashAlgorithm]
>
> HashAlgorithms: MD2 MD4 MD5 SHA1 SHA256 SHA384 SHA512
>
> I have biopython-1.58.win32-py2.7.exe:
> MD5: c4 45 46 34 3c 3d 2b 1d c9 77 24 81 74 85 84 e4
> SHA256: 2f 55 ee 34 df 39 e8 0d d7 cb 46 69 4a 1f 55 52 f1 4a 53 37 42 a0 a8
> 18 52 3b ee 6e 72 cc be 2c

Those match using the Mac command line tools:

$ md5 biopython-1.58.win32-py2.7.exe
MD5 (biopython-1.58.win32-py2.7.exe) = c44546343c3d2b1dc9772481748584e4

$ shasum -a 256 biopython-1.58.win32-py2.7.exe
2f55ee34df39e80dd7cb46694a1f5552f14a533742a0a818523bee6e72ccbe2c
biopython-1.58.win32-py2.7.exe