[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: test vectors for HMAC-SHA-1 - Test Data and Bad News -Reply
I also ran the "Hi There" message through a SHA-1 utility I developed
independently and got the same answer that BSAFE gives. As far as
the "endian-ness" convention goes, the BSAFE answer is compliant with
the test vectors given in the FIPS standard. Thus, I would contend that
the BSAFE answer is the "correct" one.
I also suspect this representation issue has something to do with the
Diffie-Hellman compatibility problem.
-John Kennedy
NOVELL, Inc.
>>> "C. Harald Koch" <chk@border.com> 02/06/97 11:53am >>>
In message <01BC1429.F844BBC0@localhost>, Edward Russell writes:
>
> BSAFE SHA:
> 4B 3A ED 5F 9F E4 01 59 B4 99 53 6F B8 A1 0C DF 3B C6 2B 4C
>
> CYLINK SHA:
> 4C 2B C6 3B DF 0C A1 B8 6F 53 99 B4 59 01 E4 9F 5F ED 3A 4B
I've seen this before. There are two different representations of hash
codes
floating around; "big endian" and "little endian". Note that the above
hashes are identical with the *bytes* listed in the opposite order.
I couldn't tell you which one is 'correct' though :-)
--
C. Harald Koch | Senior System Developer, Secure Computing
Canada Ltd.
chk@border.com | 100 University Ave., 7th Floor, Toronto ON M5J
1V6
+1 416 813 2054 (voice) | "Madness takes its toll. Please have exact
change."
+1 416 813 2001 (fax) | -Karen Murphy
<karenm@descartes.com>