]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commit
Use sha256 for hashes in the release process
authorAndreas Rammhold <andreas@rammhold.de>
Mon, 26 Oct 2020 03:03:29 +0000 (04:03 +0100)
committerSimon Marchi <simon.marchi@efficios.com>
Wed, 28 Oct 2020 14:35:28 +0000 (10:35 -0400)
commitce04ca31231138105fae3b0dda1670c6ec0e2dcb
tree7bec761f07ab8593ec8806411d8c2deae690affe
parentdd4a72c859a6896d6df824535590ccbb3631fdd7
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
ChangeLog
binutils/ChangeLog
binutils/README-how-to-make-a-release
src-release.sh