3.2. Verifying the downloaded release
There are a number of mechanisms to check the authenticity and validity of a downloaded release.
The CloudStack project provides a detached GPG signature of the release. To check the signature, run the following command:
$
gpg
--verify apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc
If the signature is valid you will see a line of output that contains 'Good signature'.
In addition to the cryptographic signature, the CloudStack provides a number of cryptographic hashes to aid in assurance of validity of the downloaded release. You can verify this hash by executing the following command:
$
gpg
--print-md MD5 apache-cloudstack-4.0.0-incubating-src.tar.bz2 | diff
- apache-cloudstack-4.0.0-incubating-src.tar.bz2.md5
If this successfully completes you should see no output. If there is any output from them, then there is a difference between the hash you generated locally and the hash that has been pulled from the server.
In addition to the MD5 hash, the CloudStack project provides a SHA512 cryptographic hash to aid in assurance of the validity of the downloaded release. You can verify this hash by executing the following command:
$
gpg
--print-md SHA512 apache-cloudstack-4.0.0-incubating-src.tar.bz2 | diff
- apache-cloudstack-4.0.0-incubating-src.tar.bz2.sha
If this command successfully completes you should see no output. If there is any output from them, then there is a difference between the hash you generated locally and the hash that has been pulled from the server.