On 27/02/2017 16:14, Richard Hipp wrote:
On 2/26/17, Ron Aaron <[email protected]> wrote:
>From a performance standpoint, I would rather see Fossil adopt the
BLAKE2 hash, as it is one of the fastest of the SHA3 finalists, and has
adjustable output hash size.

Please write and check-in code (on the "fossil-2.0" branch) that
implements BLAKE2 in a manner analogous to the code in sha1.c and
sha3.c.  I suggest a new file named "blake2.c". I will then make it an
option.

What hash length do you want for BLAKE2?  Please make the hash length
for Fossil-BLAKE2 be a multiple of 8 bits and different from 160, 228,
and 256 as those values are already assigned to other hashes.
I wish I could, but I'm so over-committed right now I can't.  Once my work-load subsides a bit I'll be happy to do that.


Ron Aaron | CTO Aaron High-Tech, Ltd | +1 425.296.0766 / +972 52.652.5543 | GnuPG Key: 91F92EB8
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to