It is essential that you verify the integrity of the downloaded
files using the PGP or MD5 signatures. Please read Verifying Apache
HTTP Server Releases for more information on why you should verify our
releases. (The same rationale applies to APR as to HTTP Server.)
The PGP signatures can be verified using PGP or GPG. First
download the KEYS
as well as the asc signature file for the particular
distribution. Make sure you get these files from the main distribution
directory, rather than from a mirror. Then verify the signatures
using
% pgpk -a KEYS
% pgpv apr-1.0.1.tar.gz.asc
or
% pgp -ka KEYS
% pgp apr-1.0.1.tar.gz.asc
or
% gpg --import KEYS
% gpg --verify apr-1.0.1.tar.gz.asc
Alternatively, you can verify the MD5 and/or SHA1 signature on the
files. An MD5 hash consists of a 32 character string (example:
d41d8cd98f00b204e9800998ecf8427e), and a SHA1 hash consists of
a 40 character string (example:
da39a3ee5e6b4b0d3255bfef95601890afd80709). To verify the hash
on a file, generate a hash string of your own on the file, and compare
the hash string you get with the hash string published inside the
signature files. A unix program called md5 or
md5sum is included in many unix distributions. It is also
available as part of
GNU
Textutils. Windows users can get binary md5 programs from here, here, or
here.
