On Mon, Apr 25, 2016 at 2:43 AM, Jeffrey Walton <[email protected]> wrote:
> > We also need to change the name of the algorithm. In FIPS 202, the name is > "SHA3-224", "SHA3-256", etc. We are currently returning "SHA-3-224" and > friends. > Probably not as crucial as the what they actually *do*, but yes it would be nice to get the names aligned as well. ;) > Yeah, I think the folks who depend on _current_ SHA3 behavior will be able > to turn to our upcoming Keccak. > Excellent. > As far as versions, I talked with David over at Bouncy Castle. They are > providing Version 3 as updated for NIST's Round 3. I don't know what Jack > Lloyd is doing at Botan, but I can ping him. I think it would be prudent if > we aligned with BC and/or Botan. > I think we need to have all the three align - us, BouncyCastle, and Botan. BouncyCastle is the de-facto standard in the Java world, and Botan is increasingly growing in popularity (and quality) in the C/C++ and Python world. So yes, if you could ping both Dave and Jack it would be great. -- Regards, Mouse -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
