Hello Tomasz
On 07.01.2014 00:29, Tomasz Sterna wrote:
Dnia 2014-01-06, pon o godzinie 22:06 +0100, Fabian Wenk pisze:
@Tomasz, could this be a "bug" or change from in jabberd 2.2.17
to 2.3.1?
In 2.3.0 GnuSASL >=1.1 dependency was introduced. So could there be an
incompatibility between your client and new GnuSASL?
I do not think so, see below.
Also since 2.3.0 CyrusSASL backend is broken. Although it is disabled by
default, there are still people using it. Are you using CyrusSASL
backend?
No, we are using the GSASL backend config option from FreeBSD
port, as the CYRUS has the remark "not supported". GnuSASL in use
is and was before with jabberd 2.2.17:
fabian@superman:~ $ pkg_info | grep sasl
gsasl-1.8.0_2 GNU SASL Library
fabian@superman:~ $
In 2.3.1 --enable-superseded and --enable-experimental defaults were
changed. So if you rely on superseeded and/or experimental features, you
need to enable them explicitly.
Enabling superseded did help and xabber could connect again with
the "use SASL authentication (recommended)" option activated.
bye
Fabian
