Hi,
I did some further testing and hacked up a little test program that
simulates the client behavior ( using a completely different SASL
implementation). Apparently the problem is at the client side (i.e
Adium/libpurple) which seems not to cleanup properly after the first
of its two
Hi,
I tried several authentication scenarios with jabberd 2.2.4 (+gsasl
0.2.29) and found that there seems to be a conflict between digest-
md5 and gssapi. I tried
- gssapi + plain (with ldapfull and PAM), which works
- digest-md5 + plain with ldapfull, which works too.
Any combination of
Dnia 2009-01-03, sob o godzinie 10:47 +0100, Andreas Hofmeister pisze:
My suspicion is that both mechanisms trash each others idea of the
authentication realm, but that is not very deeply founded.
Any idea what to try or look at next ?
1. Compile jabberd with debugging, then run c2s -D and
Am 03.01.2009 um 14:31 schrieb Tomasz Sterna:
Dnia 2009-01-03, sob o godzinie 10:47 +0100, Andreas Hofmeister pisze:
My suspicion is that both mechanisms trash each others idea of the
authentication realm, but that is not very deeply founded.
Any idea what to try or look at next ?
1.
