aboutsummaryrefslogtreecommitdiff
path: root/reproduce/software/make/build-rules.mk
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2019-07-29 20:43:20 +0100
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2019-07-29 20:52:06 +0100
commit2baf058dcf323aa07f6d5dd3214982e7fccac3da (patch)
treeb522e835217d8083a529893a9ce05a42cf2172a6 /reproduce/software/make/build-rules.mk
parent41dbf93ea0173f82b552402aa9d6636e1f1e2972 (diff)
Checking software tarball checksums before building software
Until now, there was no check on the integrity of the contents of the downloaded/copied software tarballs, we only relied on the tarball name. This could be bad for reproducibility and security, for example on one server the name of a tarball may be the same but with different content. With this commit, the SHA512 checksums of all the software are stored in the newly created `checksums.mk' (similar to how the versions are stored in the `versions.mk'). The resulting variable is then defined for each software and after downloading/copying the file we check to see if the new tarball has the same checksum as the stored value. If it doesn't the script will crash with an error, informing the user of the problem. The only limitation now is a bootstrapping problem: if the host system doesn't already an `sha512sum' executable, we will not do any checksum verification until we install our `sha512sum' (as part of GNU Coreutils). All the tarballs downloaded after GNU Coreutils are built will have their checksums validated. By default almost all GNU/Linux systems will have a usable `sha512sum' (its part of GNU Coreutils after all for a long time: from the Coreutils Changelog file atleast since 2013). This completes task #15347.
Diffstat (limited to 'reproduce/software/make/build-rules.mk')
0 files changed, 0 insertions, 0 deletions