[jdev] SASL debugging

[Norman Rasmussen]

if you have a byte array like this:  40,03,06,23

the old code generates: 403623, and it should generate 40030623

On 12/9/05, Yves Goergen <nospam.list at unclassified.de> wrote:
> On 09.12.2005 15:23 (+0100), Norman Rasmussen wrote:
> > this is breaking stuff:
> >
> > foreach (byte b in n)
> >     hex += b.ToString("x2");
> >
> > try:
> >
> > foreach (byte b in n)
> >     hex += b.ToString("x02");
>
> Sorry, this isn't it. And to be honest, I didn't expect this to make a
> difference. (What is that "0" good for anyway?) I found this call on
> dotnet247 as solution to converting stuff in hexadecimal. It's even
> already in lower-case.
>
> The whole point seems to go wrong for A1. That part is somehow
> calculated wrong. And even if I set A1 to the supposed correct value
> ("fippo" gave me his results today), still response would be wrong. Does
> Microsoft calculate MD5 somehow different? I can't see any other
> problem.... Maybe I should retry it in PHP, its MD5 function has proven
> to be correct already.
>
> --
> Yves Goergen "LonelyPixel" <nospam.list at unclassified.de>
> "Does the movement of the trees make the wind blow?"
> http://newsboard.unclassified.de - Unclassified NewsBoard Forum
>


--
- Norman Rasmussen
 - Email: norman at rasmussen.co.za
 - Home page: http://norman.rasmussen.co.za/