qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomas Restrepo" <tomas.restr...@devdeo.com>
Subject Re: Random .Net question
Date Tue, 03 Jun 2008 16:37:00 GMT
Hi Aidan,

> They bytes are generated from the MD5 of the password, which returns
> the same hex on both platforms. The problem comes when that byte[] is
> passed to the HMACMD5 constructor as the key.
> This works (ie. produces the same result as it's java cousin)
> byte[] key = new byte[]{0x7F};
> HMAC hmac = new HMACMD5(key);
> byte[] value = hmac.ComputeHash("foo");
> Changing that 0x7F to 0x80 does not.

Weird. A quick check of HMACMD5 against one of the test-cases in
RFC2202 with key bytes above 0x7F on dotnet seems to yield the right
results (just tried test3 quickly). Does it return the right result on
the Java code as well? Just curious

Tomas Restrepo

View raw message