Closed GoogleCodeExporter closed 9 years ago
I found out the issue. You have to run every 8th test in the test file. This is
because only every 8th test has the input in full bytes. Only full bytes for
input appear to be supported. That's ok though. After running quite a few of
these tests CryptoJS produces the correct hashes for Keccak v3. Great stuff.
In future, perhaps we could put these test vectors into a file and have a unit
test suite for CryptoJS.
Also if you decide to implement the actual (crippled) SHA3 standard by NIST at
some stage, perhaps you can leave this code as it is and leave it accessible
via CryptoJS.Keccak() then implement the finalized SHA3 standard as
CryptoJS.SHA3(). I know there are more than a few people that don't want to use
NIST's finalized version with faster performance but weaker security. We would
rather just use regular Keccak as was at the end of the competition. Let's keep
it how it is.
Original comment by john.f.m...@gmail.com
on 30 Apr 2014 at 4:07
Original comment by Jeff.Mott.OR
on 15 Jun 2014 at 11:14
Original issue reported on code.google.com by
john.f.m...@gmail.com
on 26 Apr 2014 at 9:31