Re: SHA1 collisions became cheaper to create.

From: Paul Hammant <paul_at_hammant.org>
Date: Wed, 15 May 2019 13:31:45 +0100

I'm suggesting phasing out SHA1, and during a v1.x to v1.x+1 upgrade
do a migration script for all content to gain (say) BLAKE2 hashes
*instead*, and for that install, client's with incompatible hashing
are rejected.

There are alternates too, where up to a moment in time a repo has
SHA1s, and thence after has some other algo.
Received on 2019-05-15 14:39:16 CEST

This message: [ Message body ]
Next message: Daniel Shahaf: "Re: SHA1 collisions became cheaper to create."
Previous message: Stefan Sperling: "Re: SHA1 collisions became cheaper to create."
In reply to: Stefan Sperling: "Re: SHA1 collisions became cheaper to create."
Next in thread: Daniel Shahaf: "Re: SHA1 collisions became cheaper to create."
Reply: Daniel Shahaf: "Re: SHA1 collisions became cheaper to create."

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]