[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#41382] [PATCH 0/6] Allow for a cryptographic hash function migratio
From: |
Leo Famulari |
Subject: |
[bug#41382] [PATCH 0/6] Allow for a cryptographic hash function migration |
Date: |
Tue, 19 May 2020 14:20:01 -0400 |
On Tue, May 19, 2020 at 08:00:34PM +0200, Marius Bakke wrote:
> This is a great initiative, and the patches LGTM.
+1
> I think that if we are to move away from SHA256, we should go with
> something that is immune to length extension attacks[0] such as BLAKE2/3
> or SHA-3 (Keccak).
I think we are so far from needing to move away from SHA256 that we
can't know what the best replacement will be when the time comes. It
will probably be quite a long time, maybe decades.
signature.asc
Description: PGP signature
- [bug#41382] [PATCH 0/6] Allow for a cryptographic hash function migration, Ludovic Courtès, 2020/05/18
- [bug#41382] [PATCH 1/6] tests: Test 'add-to-store' with several hash algorithms., Ludovic Courtès, 2020/05/18
- [bug#41382] [PATCH 3/6] guix hash, guix download: Add '--hash'., Ludovic Courtès, 2020/05/18
- [bug#41382] [PATCH 2/6] tests: Test fixed-output derivations with several hash algorithms., Ludovic Courtès, 2020/05/18
- [bug#41382] [PATCH 5/6] packages: Add 'sha512' optional field to <origin>., Ludovic Courtès, 2020/05/18
- [bug#41382] [PATCH 4/6] guix hash, guix download: Support base64 format., Ludovic Courtès, 2020/05/18
- [bug#41382] [PATCH 6/6] packages: Add 'base64' macro., Ludovic Courtès, 2020/05/18
- [bug#41382] [PATCH 0/6] Allow for a cryptographic hash function migration, Ludovic Courtès, 2020/05/19