On Tuesday 07 January 2014 00:29:50 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?
Mind you, xabber is not the only client affected, yaxim cannot connect either.
> 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?
I am using GnuSASL:
# ldd /usr/bin/jabberd2-s2s
libssl.so.1.0.0 => /usr/lib/libssl.so.1.0.0 (0xf7e38000)
libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0 (0xf7ca0000)
libgsasl.so.7 => /usr/lib/libgsasl.so.7 (0xf7c74000)
libudns.so.0 => /usr/lib/libudns.so.0 (0xf7c50000)
libidn.so.11 => /usr/lib/libidn.so.11 (0xf7c1c000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0xf7be0000)
libz.so.1 => /lib/libz.so.1 (0xf7bb8000)
libc.so.6 => /lib/libc.so.6 (0xf7a28000)
libdl.so.2 => /lib/libdl.so.2 (0xf7a10000)
/lib/ld-linux.so.2 (0xf7ea4000)
Guido
