|
Size: 2727
Comment: Complete Rework in same structure
|
Size: 4997
Comment: improve phrasing of what should be compared
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Check integrity of Gpg4win packages = You can check packages by their SHA1 Checksum, by OpenPGP Singature (if you already have GnuPG installed) or by the Code Signing Certficate. The Checksums and Information you need to verify your downloaded package files, are available on the [[https://www.gpg4win.org/package-integrity.html|Gpg4Win package integrity]] site. |
= 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. **Using one method is good enough.** |
| Line 6: | Line 10: |
| == SHA1 checksums == | == Code Signing Certificate (recommended) All Gpg4win installer files since April 2016 are code signed. Look at [[https://www.gpg4win.org/package-integrity.html|Gpg4win package integrity]] to see which is the name and the certificate of the publisher (for the date the package was signed). Windows can check the integrity and show the publisher of a signed software package. Compare this to what you have looked up. |
| Line 8: | Line 17: |
| Once you downloaded the file from [[https://www.gpg4win.org/|Gpg4Win.org]], you can verify its SHA1 checksums. On machines that run Windows 8 or newer, you can recieve the desired output, by opening a command line, navigate to your Download-Folder and put in the line: | Optional for some additional safety: compare the certificate of the publisher not just by name, but also by using the SHA~256 hash checksum of the certificate (aka {{{sha2_fpr}}}). |
| Line 10: | Line 20: |
| {{{certutil -hashfile FileToHash.exe sha1}}} | ==== Method A: UAC (recommended) When trying to run the installer on Windows, the **User Access Control dialog will show the publisher**. (If you have disabled User Access Control use a different method.) |
| Line 12: | Line 25: |
| On Systems that run older operating systems, then Windows 8: Install a certain [[https://support.microsoft.com/en-us/kb/934576?spid=12925&sid=1569|Windows Patch]], wich delivers the functionality. | ==== Method B: file properties A second way to show the publisher is to use the file properties in the explorer. Right click on the installer -> properties -> digital signatures -> Details of signatures. (Try this if no publisher is shown by the UAC in rare cases after a download with Firefox or Iridium (Chromium). For details see [[https://dev.gnupg.org/T3379|T3379]].) |
| Line 14: | Line 31: |
| Once you entered the operation, the command line will return an alphanumeric string, which yu can compare to the one on the [[https://www.gpg4win.org/package-integrity.html|Gpg4Win package integrity]] site. | ==== Method C: signtool A third way if the previous methods do not work: use [[https://msdn.microsoft.com/en-us/library/windows/desktop/aa387764(v=vs.85).aspx|MSDN:SignTool]] which is a part of the Microsoft development tools: Open open a command line, navigate to the folder and enter |
| Line 16: | Line 37: |
| == OpenPGP signatures == | {{{SignTool verify /pa /v gpg4win*.exe}}} |
| Line 18: | Line 39: |
| 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 [[https://www.gpg4win.org/package-integrity.html|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 | Now you should see which certificate signed the installer and you can compare the publisher. == 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 use a command like the following, but adapt the filename to the version you have downloaded and you want to check: {{{certutil -hashfile gpg4win-3.1.15.exe sha256}}} 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. It has to match for all hexadecimal digits. (Sometimes colons or spaces are used to group the checksum.) Make sure to compare it to the checksum with the right algorithm (SHA-256). ==== If the tool does not work ... see of you have a different tool that can calculate SHA-256 checksums on your machine and use it instead. 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. Less reliable is falling back using {{{sha1}}} stead of the {{{sha256}}} in the above command line and comparing it to the SHA-1 checksum. Some elder versions of Windows may not come with a standard tool to calculate SHA-256 and we still publish SHA-1 checksums because checking against them is better than not checking with a cryptographic checksum. == 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 [[https://www.gpg4win.org/package-integrity.html|Gpg4win package integrity]] site. The pubkey, with which the files are signed, is also given on that page. You have to import the public key and now you can validate the signature of the file with the command |
| Line 22: | Line 73: |
| == File lengths == Navigate to the folder, where you downloaded the Gpg4Win packages to, and enter |
== File lengths (as diagnostics) This is not a verification method, but I way trying to find out why a method my have failed. One cause of a bad download is that the internet connection broke down during the download. In this case the size of the file on your harddisk is smaller than it should be. Navigate to the folder, where you downloaded the Gpg4win packages to, and enter |
| Line 27: | Line 82: |
| The command will list all files and their sizes in the directory. You can then compare those results with the sizes given on the [[https://www.gpg4win.org/package-integrity.html|Gpg4Win package integrity]] site. | The command will list all files and their sizes in the directory. You can then compare those results with the sizes given on the [[https://www.gpg4win.org/package-integrity.html|Gpg4win package integrity]] site. |
| Line 29: | Line 84: |
| == Code Signing Certificate == | This can help you spot a corrupt file where the downloading got aborted or something. It will not protect you against an attacker. |
| Line 31: | Line 87: |
| All Gg4win installer files since April 2016 that can be downloaded via [[https://www.gpg4win.org/|Gpg4Win.org]] are code signed. The signature informations used to code sing the packages can be found on the [[https://www.gpg4win.org/package-integrity.html|Gpg4Win package integrity]] site. To verify the integrity, you open a command line, navigate to the folder and enter {{{SignTool verify gpg4win*.exe}}} |
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. Using one method is good enough.
Contents
Code Signing Certificate (recommended)
All Gpg4win installer files since April 2016 are code signed. Look at Gpg4win package integrity to see which is the name and the certificate of the publisher (for the date the package was signed). Windows can check the integrity and show the publisher of a signed software package. Compare this to what you have looked up.
Optional for some additional safety: compare the certificate of the publisher not just by name, but also by using the SHA256 hash checksum of the certificate (aka sha2_fpr).
Method A: UAC (recommended)
When trying to run the installer on Windows, the User Access Control dialog will show the publisher. (If you have disabled User Access Control use a different method.)
Method B: file properties
A second way to show the publisher is to use the file properties in the explorer. Right click on the installer -> properties -> digital signatures -> Details of signatures. (Try this if no publisher is shown by the UAC in rare cases after a download with Firefox or Iridium (Chromium). For details see T3379.)
Method C: signtool
A third way if the previous methods do not work: 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 /pa /v gpg4win*.exe
Now you should see which certificate signed the installer and you can compare the publisher.
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 use a command like the following, but adapt the filename to the version you have downloaded and you want to check:
certutil -hashfile gpg4win-3.1.15.exe sha256
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. It has to match for all hexadecimal digits. (Sometimes colons or spaces are used to group the checksum.) Make sure to compare it to the checksum with the right algorithm (SHA-256).
If the tool does not work
... see of you have a different tool that can calculate SHA-256 checksums on your machine and use it instead.
On systems that run older operating systems than Windows 8: Install a certain Windows Patch, which delivers the functionality.
Less reliable is falling back using sha1 stead of the sha256 in the above command line and comparing it to the SHA-1 checksum. Some elder versions of Windows may not come with a standard tool to calculate SHA-256 and we still publish SHA-1 checksums because checking against them is better than not checking with a cryptographic checksum.
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 pubkey, with which the files are signed, is also given on that page. You have to import the public key and now you can validate the signature of the file with the command
gpg --verify gpg4win*.exe.sig gpg4win*.exe
File lengths (as diagnostics)
This is not a verification method, but I way trying to find out why a method my have failed. One cause of a bad download is that the internet connection broke down during the download. In this case the size of the file on your harddisk is smaller than it should be.
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