> > (1) Is it OK to change SHA-3 to align it with FIPS 202? > > Sure, but we should do it with the aligned with the usual versioning / > warning practices, like we discussed with ECIES. Deprecate the current > version if we do a 5.7 and evaluate again if we are doing a direct 6.0 > whether it would be too rude to break the existing "SHA-3". >
Done at: * http://github.com/weidai11/cryptopp/commit/2b311f21944bfda0e2b5b5229a098903c4ac2252 * http://github.com/weidai11/cryptopp/commit/920b23d884e684864ec6b7e79129a59ea9df5442 Jeff -- -- 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.
