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
e1c41605b0a359759059e4e2f527055b0f4036d5 gpg4win-1.1.4.exe 6ae2b32ec97801543e954fd23888fa10a9a1781a gpg4win-light-1.1.4.exe 08c585347750e8345d964afa73aff7d455c81f39 gpg4win-src-1.1.4.exe 6a3ec8f7cb5a4252b3b93f49b733bcb5e344eb06 gpg4win-1.1.4.tar.bz2
MD5 checksums
b2e18fd37a14b065a8361f5348c83f72 gpg4win-1.1.4.exe bb3bee4d8c30f5376d532c7135b17045 gpg4win-light-1.1.4.exe 2efc36781e7b3f463064129d6819fe4d gpg4win-src-1.1.4.exe 2b1ac6dbc4d4fe3e710348b7a671b102 gpg4win-1.1.4.tar.bz2
OpenPGP signatures
For gpg4win-1.1.4.exe: http://ftp.gpg4win.org/gpg4win-1.1.4.exe.sigFor gpg4win-light-1.1.4.exe: http://ftp.gpg4win.org/gpg4win-light-1.1.4.exe.sig
For gpg4win-src-1.1.4.exe: http://ftp.gpg4win.org/gpg4win-src-1.1.4.exe.sig
For gpg4win-1.1.4.tar.bz2: gpg4win-1.1.4.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:10013309 bytes for gpg4win-1.1.4.exe 6162821 bytes for gpg4win-light-1.1.4.exe 61946788 bytes for gpg4win-src-1.1.4.exe 4473200 bytes for gpg4win-1.1.4.tar.bz2
