-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Wed, 28 Oct 2015 at 5:37pm, Eduard wrote:
> Hi, > > I wish to discuss the issues surrounding the use of SHA1 in Fossil and > their consequences, as well as propose several possibilities to deal > with them. > <snip-snip> > > As for the exact value of BetterHash, I would like to nominate > BLAKE2b-512 [2]. It is faster than both MD5 and SHA1, it is based upon > BLAKE which has received a lot of cryptanalytic attention during the > SHA3 competition, and it retains a large security margin (the best > (academic) attack to date is on a reduced version that does only 2.5 > rounds instead of 10, and even then only downgrades the security from > 512 to 481 bits). What kind of speed hit would using the BLAKE2b algorithm on 32-bit machines such as i386, vax, or m68k? Yes, there's the BLAKE2s algorithm for 8-32 bit architectures but that produces different hashes than BLAKE2b. Is it even possible to use BLAKE2b on a 32-bit CPU? > > Please let me know your thoughts on this matter. > > Best regards, > Eduard > > [1] https://sites.google.com/site/itstheshappening/ > [2] https://blake2.net/ > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > - -- Christopher M. Fuhrman [email protected] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0 Comment: GPGTools - http://gpgtools.org iQEcBAEBCAAGBQJWMoDyAAoJEJMBHfiIBijRtEEH/iSc9bDaJR2HlJIWwFV6uIws pwotLs9W6fwcZoLz++ofd+V03p3gJC5wrYWEEeBHGlnGUA9InUudKG8NGvHqOju3 nS+lFeHf2eDDGV8/oZQF8lmjm751+WRDSi5TB+fmhgVaKmdMTLQmymw1Il+MmfFI 1uqAV1GGg4A89x+ER9mMFBpRKpTyP5jFq/NhPYQzUyXyPeoSxTesafAWFTL89fCP /ShpwsAUeUc8i9PDFDhRApT4grMwQ+R+c8VH5NNoTcMo47hXCuhjCALLNOSKhztw FPOJm5xS7IykiFaF9Tx0+M365hMbcO/9iu9X5eqbhfjQ3VLd7gqL4ntLcpu5xgY= =cXkl -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
