aboutsummaryrefslogtreecommitdiff
path: root/ChangeLog
diff options
context:
space:
mode:
authorAndreas Rammhold <andreas@rammhold.de>2020-10-26 04:03:29 +0100
committerSimon Marchi <simon.marchi@efficios.com>2020-10-28 10:35:28 -0400
commitce04ca31231138105fae3b0dda1670c6ec0e2dcb (patch)
tree7bec761f07ab8593ec8806411d8c2deae690affe /ChangeLog
parentdd4a72c859a6896d6df824535590ccbb3631fdd7 (diff)
downloadgdb-ce04ca31231138105fae3b0dda1670c6ec0e2dcb.zip
gdb-ce04ca31231138105fae3b0dda1670c6ec0e2dcb.tar.gz
gdb-ce04ca31231138105fae3b0dda1670c6ec0e2dcb.tar.bz2
Use sha256 for hashes in the release process
I just came across the GDB 10.1 release notes and saw that md5 is still being used in those. I thought it would be a good idea to instead have a more modern, secure and wildly available hash function such as SHA256 as part of the release process. The changes have been done rather mechnically via sed but executing the `src-release.sh -b gdb` did work so I am confident about the result. While this does not directly address the release mails, I was wasn't able to find the template/script used for those, this is probably still an improvement. ChangeLog: * src-release.sh: Use sha256sum instead of md5sum. binutils/ChangeLog: * README-how-to-make-a-release: Use sha256sum instead of md5sum. Change-Id: I9cf19ea40699137c45463b8514f6e29271af2347
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog4
1 files changed, 4 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index 9daa7be..c9a2f336 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2020-10-26 Andreas Rammhold <andreas@rammhold.de>
+
+ * src-release.sh: Use sha256sum instead of md5sum.
+
2020-10-14 Andrew Burgess <andrew.burgess@embecosm.com>
* Makefile.in: Rebuild.