These source archives are generated from tagged releases.
|Version||Release Date||Source Code||PGP||SHA|
# Verify the Integrity of the Files
It is essential that you verify the integrity of the downloaded file using the
PGP signature (
.asc file) or a hash (
.sha* file). Please read
Verifying Apache Software Foundation Releases
for more information on why you should verify our releases.
The PGP signature can be verified using PGP or GPG. First download the KEYS as well as the asc signature file for the relevant distribution. Make sure you get these files from the main distribution site, rather than from a mirror. Then verify the signatures using
$ gpg --import KEYS $ gpg --verify downloaded_file.asc downloaded_file
$ pgpk -a KEYS $ pgpv downloaded_file.asc
$ pgp -ka KEYS $ pgp downloaded_file.asc
Alternatively, you can verify the hash on the file.
Hashes can be calculated using GPG:
$ gpg --print-md SHA256 downloaded_file
The output should be compared with the contents of the SHA256 file. Similarly for other hashes (SHA512, SHA1, MD5 etc) which may be provided.
Windows 7 and later systems should all now have
$ certUtil -hashfile pathToFileToCheck
Unix-like systems (and macOS) will have a utility called