|Where is sha3deep? The Standardization Process
||[Aug. 7th, 2013|10:01 am]
You might think that because NIST chose KECCAK to be SHA-3 standard that we can all start using SHA-3 right away. Unfortunately it's not quite that simple. In my last post on the topic I mentioned a few "flavors" of SHA-3. These correspond to input parameters to the underlying algorithm. They control the performance of the code and the size of the output. As you might imagine, there is an inverse relationship between performance and resistance to attack. The KECCAK team gave a detailed talk on these issues in February .
NIST will eventually make a decision about these trade offs and declare one (or more) standard versions of SHA-3 in a Federal Information Processing Standard (FIPS). When that document is released, I can get to work making a sha3deep .
The NIST standardization process is not opaque! Later this fall NIST will have a public comment period before making a decision in 2014 . I strongly encourage you to make your opinions known to NIST. The opinions of practitioners—the people who are going to be using the algorithm—matter as much as the opinions of mathematicians.
 There is some experimental SHA-3 code in the Hashdeep git repo now, but you don't want to use it.