I'm happy to see you thinking along those lines. >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.
On 27/02/2017 3:48, Richard Hipp wrote: > On 2/26/17, Tony Papadimitriou <to...@acm.org> wrote: >> how urgent is the need to >> transition away from SHA1? >> > From a technical standpoint, it is not very urgent, in my assessment. > > However, from a PR standpoint, I think it needs to happen quickly. > > It can also be a big PR win if we are able to boast that Fossil > transitioned away from SHA1 painlessly, quickly, and efficiently and > without breaking any legacy. > *Ron Aaron | * CTO Aaron High-Tech, Ltd <http://8th-dev.com> | +1 425.296.0766 / +972 52.652.5543 | GnuPG Key: 91F92EB8 <https://pgp.mit.edu/pks/lookup?op=get&search=0xC90C1BD191F92EB8>
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
