Re: test vectors for HMAC-SHA-1 - Test Data and Bad News -Reply
John Kennedy <JKENNEDY@novell.com> Thu, 06 February 1997 21:10 UTC
Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id QAA14039 for ipsec-outgoing; Thu, 6 Feb 1997 16:10:59 -0500 (EST)
Message-Id: <s2f9e721.084@novell.com>
X-Mailer: Novell GroupWise 4.1
Date: Thu, 06 Feb 1997 14:13:27 -0700
From: John Kennedy <JKENNEDY@novell.com>
To: chk@border.com, erussell@ftp.com
Cc: ipsec@tis.com
Subject: Re: test vectors for HMAC-SHA-1 - Test Data and Bad News -Reply
Sender: owner-ipsec@ex.tis.com
Precedence: bulk
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> Received: by provo.mx.relay with Novell_GroupWise; Thu, 06 Feb 1997 13:03:22 -0700 Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id NAA13010 for ipsec-outgoing; Thu, 6 Feb 1997 13:49:13 -0500 (EST) Message-Id: <97Feb6.135047est.30800-3@janus.border.com> References: <01BC1429.F844BBC0@localhost> In-reply-to: Your message of "Thu, 06 Feb 1997 12:33:16 -0500". <01BC1429.F844BBC0@localhost> Organization: Secure Computing Canada Ltd. Phone: +1 416 813 2054 X-uri: <URL:http://www.eng.border.com/homes/chk/> X-Face: )@F:jK?*}hv!eJ}*r*0DD"k8x1.d#i>7`ETe2;hSD2T!:Fh#wu`0pW7lO|Dfe'AbyNy[\Pw z'.bAtgTM!+iq2$yXiv4gf<:D*rZ-|f$\YQi7"D"=CG!JB?[^_7v>8Mm;z:NJ7pss)l__Cw+.>xUJ) did@Pr9 Sender: owner-ipsec@ex.tis.com Precedence: bulk Date: Thu, 06 Feb 1997 11:53:02 -0700 From: "C. Harald Koch" <chk@border.com> To: erussell@ftp.com Cc: ipsec@tis.com Subject: Re: test vectors for HMAC-SHA-1 - Test Data and Bad News 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>
- Re: test vectors for HMAC-SHA-1 - Test Data and B… John Kennedy