Re: [PATCH] MINOR: Generate sha256 checksums in publish-release

2018-07-20 Thread Willy Tarreau
On Fri, Jul 20, 2018 at 01:45:51PM +0200, Tim Düsterhus wrote: > Perfect. Could you possibly retroactively add a .sha256 file for the > newest version of each currently supported branch (i.e. 1.8.12, 1.7.11, > 1.6.14 and 1.5.19)? This would allow me to update a few scripts, without > having to

Re: [PATCH] MINOR: Generate sha256 checksums in publish-release

2018-07-20 Thread Tim Düsterhus
Willy, Am 20.07.2018 um 10:50 schrieb Willy Tarreau: > Makes sense, now merge. > Perfect. Could you possibly retroactively add a .sha256 file for the newest version of each currently supported branch (i.e. 1.8.12, 1.7.11, 1.6.14 and 1.5.19)? This would allow me to update a few scripts, without

Re: [PATCH] MINOR: Generate sha256 checksums in publish-release

2018-07-20 Thread Willy Tarreau
Hi Tim, On Thu, Jul 19, 2018 at 11:57:56PM +0200, Tim Duesterhus wrote: > Currently only md5 signatures are generated. While md5 > still is not broken with regard to preimage attacks, sha256 > clearly is the current secure solution. > > This patch should be backported to all supported branches.

[PATCH] MINOR: Generate sha256 checksums in publish-release

2018-07-19 Thread Tim Duesterhus
Currently only md5 signatures are generated. While md5 still is not broken with regard to preimage attacks, sha256 clearly is the current secure solution. This patch should be backported to all supported branches. --- scripts/publish-release | 7 --- 1 file changed, 4 insertions(+), 3