Simon Josefsson simon@josefsson.org writes:
Should I try to make it compatible with libgcrypt, and presumably Serpent-1?
It ought to be serpent-1, the algorithm proposed for AES. RFC 4344 references the algorithm like this:
[SERPENT] Anderson, R., Biham, E., and Knudsen, L., "Serpent: A proposal for the Advanced Encryption Standard", NIST AES Proposal, 1998.
Thus modifying serpent-test.c? I'll send a patch later.
I've already checked in a few new test cases in serpent-test.c (taken from http://www.cs.technion.ac.il/~biham/Reports/Serpent/), but #if:ed out for now.
I'd also like to hear what response we get from the serpent people regarding conflicting test vectors, it seems so strange if the test vectors in the aes submission were broken.
Regards, /Niels