[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: test vectors for HMAC-SHA-1 - Test Data and Bad News
The string and digest are taken from FIPS PUB 180-1.
Our code comes up with same as BSAFE... and conforms to the test vectors
give here...
// Test vectors
static const char k_testString[] = // Must be declared char for UNIX
compiler
"abcdbcdecdefdefgefghfghighijhijkijkljklmklmnlmnomnopnopq";
static const BYTE k_correctDigest[SHA_DIGEST_SIZE] = {
0x84, 0x98, 0x3E, 0x44, 0x1C, 0x3B, 0xD2, 0x6E, 0xBA, 0xAE,
0x4A, 0xA1, 0xF9, 0x51, 0x29, 0xE5, 0xE5, 0x46, 0x70, 0xF1
};
----
Greg Carter
Entrust Technologies
carterg@entrust.com
>
>O.K., O.K., C. Harald Koch gets the "Mirror Image" award for spotting what
>should have been obvious to us. But understand, we're running on only a
>handful of hours of sleep trying to get us all to interoperate. :-) I don't
>think
>I would characterize this as an "endian" problem though as that as more
>to do with byte arrangement within shorts and longs - I doubt the problem
>is caused by one platform compiled with the wrong byte order defined.
>
>This is good news in that we won't need cryptographers and mathematicians
>to analyze or hand perform the correct results. We just need a decision on
>which way is to be deemed the "correct" way. I have a coin...
>
>We'll try to establish if the same is true at the end of a Diffie Hellman
>exchange,
>but that will be a little trickier.
>
>
>