Oh, and Yes, Eric.... Your mail came literally 2 minutes after I found the problem....... I wish you would have checked the ML 2 hours before :-) Thanks anyways! This confirms the bug.
On Tue, Feb 23, 2010 at 8:48 PM, StuFF mc <[email protected]> wrote: > So yeah, I can confirm. Today: > > - I figured out I would need the MU thingy - Jabberd itself wasn't gonna > make it - the next time I'll take a Jabber having built in MU ;) > - I spent about an hour with the current maintainer of the mu-conference > component to try to figure out > - I then wrote here where Reinhard very bravely tried to help me isolate > the problem > - At a point he said something about the secret where I realize it was the > only thing we must have had different, so I went using a very simple one > > Bingo! Has anybody some kind of URL pointer refering to the bug? :( I'm > gonna tweet about it (and inform the maintainer of MU), but I'd like to have > some kind of bug report where I can confirm this. > > > > On Tue, Feb 23, 2010 at 7:18 PM, Reinhard Max <[email protected]> wrote: > >> >> On Tue, 23 Feb 2010 at 18:28, Eric Schnoebelen wrote: >> >> How long is the secret? There is/was at least one bug on the secret >>> processing code of some component that would cause such an error if the >>> secret was *exactly* some even number of characters long. >>> >> >> yep, that was it. >> >> Two minutes before your post arrived we found that it works for StuFF mc >> when he uses a much shorter secret than the 41 characters he had. :) >> >> I did some more tests and found that it fails when the password is 16 >> characters or longer, but couldn't find what's causing that limit when >> glancing over the respective areas in the router and mu-conference code. >> >> >> cu >> Reinhard >> >> >> -- >> To unsubscribe send a mail to >> [email protected]<jabberd2%[email protected]> >> >> >
