> We spun-up a Keccack branch > http://github.com/weidai11/cryptopp/tree/keccak. It accomplishes two > things. First, we added a `Keccak` class that provides the former NIST > behavior, before FIPS 202 was finalized. Second, we changed SHA3 to conform > to FIPS 202. The macro CRYPTOPP_USE_FIPS_202_SHA3 is no longer needed. > > Related to (2), we also changed the Algorithm Name of SHA3 from the string > `SHA-3-NNN` to `SHA3-NNN`. There was an extra hyphen that was less > conforming. > > We are still up in the air with respect to sponge functions (other than > F1600) and XOFs. We don't really have an idea of how they should look at > the design and implementation level for software. (I have some ideas in the > back of my head). However, perfection should not be the enemy of the good, > so we pulled the trigger and provided Keccak. > > The Visual Studio project files were modified. However, vs2010.zip was not > updated. keccack.h and keccak.cpp should be added by hand to the > cryptlib.vcxproj only from vs2010.zip >
The initial testing of Keccak went well. It was fine on both Linux and Windows from the command line. Windows command line testing uses VC++ build tools from the command line and 'cryptest.nmake' (http://github.com/weidai11/cryptopp/blob/master/cryptest.nmake). If there are no objections, I'll merge this soon. 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.
