summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDylan Baker <dylan@pnwbakers.com>2019-10-24 09:43:07 -0700
committerDylan Baker <dylan@pnwbakers.com>2019-10-24 09:43:07 -0700
commit8cd77d79b12cb802a3eda0fdd6f7ce11662d02e2 (patch)
tree0ba0a3f38d8e600df8b1332e80defbcc9c46b037
parent5fe2dea278196cd7e1894212ad229446332f00e7 (diff)
release: Remove MD5 and SHA1 sums from announce email
These are old and insecure. We already provide sha256 and sha512 hashes, so removing these shouldn't be a problem. Sha1 is still used by jh, and I don't know what to do there, so I've left the program, but removed it from the announce template.
-rwxr-xr-xrelease.sh3
1 files changed, 0 insertions, 3 deletions
diff --git a/release.sh b/release.sh
index 74e339d..86d0d49 100755
--- a/release.sh
+++ b/release.sh
@@ -129,8 +129,6 @@ RELEASE
tarball=`basename $tarball`
cat <<RELEASE
https://$host_current/$section_path/$tarball
-MD5: `$MD5SUM $tarball`
-SHA1: `$SHA1SUM $tarball`
SHA256: `$SHA256SUM $tarball`
SHA512: `$SHA512SUM $tarball`
PGP: https://${host_current}/${section_path}/${tarball}.sig
@@ -740,7 +738,6 @@ process_module() {
echo "Info: skipped pushing tag \"$tag_name\" to the remote repository in dry-run mode."
fi
- MD5SUM=`which md5sum || which gmd5sum`
SHA1SUM=`which sha1sum || which gsha1sum`
SHA256SUM=`which sha256sum || which gsha256sum`
SHA512SUM=`which sha512sum || which gsha512sum`