Different SHA1 Checksum using Microsoft file checksum integrity verifier

W Wong wwongwong2013 at gmail.com
Sat Jan 23 11:58:49 CET 2016


Greeting all:

I downloaded the Gpg4win 2.3.0 (Released: 2015-11-25)

from https://www.gpg4win.org/download.html


I did a checksum using Microsoft file checksum integrity verifier as
follows:

C:\Users\edsw\utility>fciv.exe ..\..\Downloads\gpg4win-2.3.0.exe

//

// File Checksum Integrity Verifier version 2.05.

//

4a88f90a01b0ba8e3eb0073f7b6a4bfb ..\..\downloads\gpg4win-2.3.0.exe


The checksum is different from the one announced on the site


SHA1 checksum (for gpg4win2.3.0.exe):
88d90ee9a1ea3e66b198ea866063140b882444d5


I believe that nothing has been tampered with the version  gpg4win-2.3.0.exe
that I have downloaded. Is there any reason why the Microsoft file checksum
integrity verifier (fciv) will produce a different checksum?


May be the checksum announced on the https://www.gpg4win.org/download.html

has not been updated for a while???


Please comment.  Thanks in advance for your assistance with my query


Best regards,


Wyatt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20160123/2052a554/attachment.html>


More information about the Gnupg-users mailing list