Check integrity of Gpg4win packages
How to actually perform the checks can be found e.g. on the GnuPG web page on integrity checks.SHA1 checksums
1fb338f4e5fa06c72736e9ebaebea8fbc0e3618a gpg4win-1.1.3.exe 3487e36ddba913fb4bb8aed44e8740ed3dd8815d gpg4win-light-1.1.3.exe aecf06075548c325ecd93651340418edf0b03c21 gpg4win-src-1.1.3.exe cac3c3da565c1cecefaabef75bbaac7baff8f741 gpg4win-1.1.3.tar.bz2
MD5 checksums
fe86ed13810896ec9fb8eea29401d14d gpg4win-1.1.3.exe 4f0c0dbdf5affe94a4a7a37e4dab447e gpg4win-light-1.1.3.exe 311b53aedc01ce25c31b619803113360 gpg4win-src-1.1.3.exe ba5ca81edc7799931df4b5f4db2a4a68 gpg4win-1.1.3.tar.bz2
OpenPGP signatures
For gpg4win-1.1.3.exe: http://ftp.gpg4win.org/gpg4win-1.1.3.exe.sigFor gpg4win-light-1.1.3.exe: http://ftp.gpg4win.org/gpg4win-light-1.1.3.exe.sig
For gpg4win-src-1.1.3.exe: http://ftp.gpg4win.org/gpg4win-src-1.1.3.exe.sig
For gpg4win-1.1.3.tar.bz2: gpg4win-1.1.3.tar.bz2.sig which can be found here.
The signatures have been created with the key with the ID 1CE0C630 and can be retrieved from PGP keyservers.
Loading a key from a keyserver can be done e.g. via GPA or WinPT. Checking the the signature of a file is best done with GPGee via the Explorer.
File lengths
If you have a mismatch on the checksum or a bad signature you should first verify that you really downloaded the complete file. Here are the lengths you should get:9717767 bytes for gpg4win-1.1.3.exe 5984378 bytes for gpg4win-light-1.1.3.exe 59790276 bytes for gpg4win-src-1.1.3.exe 4469205 bytes for gpg4win-1.1.3.tar.bz2
