|
Size: 3578
Comment: typo
|
Size: 3776
Comment: improve. Make sha256 the default, warn for filelength
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 32: | Line 32: |
| == SHA1 checksums | == Checksums |
| Line 34: | Line 34: |
| Once you downloaded the file from [[https://www.gpg4win.org/|Gpg4Win.org]], you can verify its SHA~1 checksums. On machines that run Windows 8 or newer, you can receive the desired output, by opening a command line, navigate to your Download-Folder and put in the line: | Once you have downloaded the file, you can verify that it matches the published checksums (that you have gotten via a trusted channel). Open a command line, navigate to your Download-Folder and put in the line: |
| Line 36: | Line 36: |
| {{{certutil -hashfile FileToHash.exe sha1}}} | {{{certutil -hashfile gpg4win-3.1.7.exe sha256}}} |
| Line 38: | Line 38: |
| On Systems that run older operating systems, than Windows 8: Install a certain [[https://support.microsoft.com/en-us/kb/934576?spid=12925&sid=1569|Windows Patch]], which delivers the functionality. | If this does not work, try {{{sha1}}} instead of {{{sha256}}}. (SHA-256 is to be preferred, but we are not aware of a standard Microsoft tool to check SHA-256 for elder versions of Windows. If you have a different tool available to check SHA-256 checksums, you can use it.) |
| Line 40: | Line 41: |
| Once you entered the operation, the command line will return an alphanumeric string, which you can compare to the one on the [[https://www.gpg4win.org/package-integrity.html|Gpg4Win package integrity]] site. | On systems that run older operating systems, than Windows 8: Install a certain [[https://support.microsoft.com/en-us/kb/934576?spid=12925&sid=1569|Windows Patch]], which delivers the functionality. |
| Line 42: | Line 43: |
| (These instructions are written for SHA-1 and not the stronger SHA-256 because we are not aware of standard Microsoft tools to check SHA-256 for elder versions of Windows. If you have a tool to check SHA-256, use it instead.) |
Once you have entered the command, it will return an alphanumeric string, which you can compare to the one on the [[https://www.gpg4win.org/package-integrity.html|Gpg4Win package integrity]] site. Make sure to compare it to the checksum with the same algorithm (SHA-256 or SHA-1). |
| Line 60: | Line 60: |
| This can help you spot a corrupt file where the downloading got aborted or something. It will not protect you against an attacker. |
Check integrity of Gpg4win packages
You shall only run applications on your computer that you trust. This page shows several methods to check that the software called Gpg4win that you have just downloaded originates from the Gpg4win Initiative.
Contents
Code Signing Certificate
All Gg4win installer files since April 2016 are code signed. The signature informations used to code sign the packages can be found on the Gpg4Win package integrity site. Windows can check the integrity and the publisher of a signed software package.
Method A: UAC
When trying to run the installer on Windows, the User Access Control dialog will show the publisher, check that is the one you expected it to be. :) (If you have disabled User Access Control use a different method.)
Method B: file properties
A second way is to use the file properties in the explorer. Right click on the installer -> properties -> digital signatures -> Details of signatures. Use this with Firefox or Iridium (Chromium) until T3379 is solved.
Method C: signtool
A third way is to use MSDN:SignTool which is a part of the Microsoft development tools: Open open a command line, navigate to the folder and enter
SignTool verify gpg4win*.exe
Checksums
Once you have downloaded the file, you can verify that it matches the published checksums (that you have gotten via a trusted channel). Open a command line, navigate to your Download-Folder and put in the line:
certutil -hashfile gpg4win-3.1.7.exe sha256
If this does not work, try sha1 instead of sha256. (SHA-256 is to be preferred, but we are not aware of a standard Microsoft tool to check SHA-256 for elder versions of Windows. If you have a different tool available to check SHA-256 checksums, you can use it.)
On systems that run older operating systems, than Windows 8: Install a certain Windows Patch, which delivers the functionality.
Once you have entered the command, it will return an alphanumeric string, which you can compare to the one on the Gpg4Win package integrity site. Make sure to compare it to the checksum with the same algorithm (SHA-256 or SHA-1).
OpenPGP signatures
If you upgrade your Gpg4Win version, you already have gnupg installed and you can verify the integrity of the downloaded file, by its OpenPGP signature. To do so, you have to download, next the file, the signature of the file. You'll find the download-links on the Gpg4Win package integrity site. The Key, with which the files are signed, is also given on that page. You have to import the key and now you can validate the signature of the file with the command
gpg --verify gpg4win*.exe.sig gpg4win*.exe
File lengths
Navigate to the folder, where you downloaded the Gpg4Win packages to, and enter
dir
The command will list all files and their sizes in the directory. You can then compare those results with the sizes given on the Gpg4Win package integrity site.
This can help you spot a corrupt file where the downloading got aborted or something. It will not protect you against an attacker.
Troubleshooting
If you encounter any problems, please feel free to ask them at the forums or on the mailinglist. If you already figured out, how to fix your issue, please leave your answer here