Re: Cannot connect with android clients xabber or yaxim to jabberd2
Hello Guido On 08.01.2014 21:01, Guido Winkelmann wrote: On Monday 06 January 2014 22:06:32 Fabian Wenk wrote: A friend also had the problem with his xabber client connecting after he did upgrade jabberd from 2.2.17 to 2.3.1. After I have just discussed this issue with him again (as I did not had any problems, but I do not use it from Android), he pocked around in the settings and did deactivate the option (translated from German): use SASL authentication (recommended) (deactivate for very old servers) in xabber and he is able to connect again. You are right, if I disable SASL auth, I can login via xabber again. Tomasz had a private conversation with me. Our conclusion was, that this must be a bug or wrong implementation or translation in xabber. According to Tomasz the '--enable-superseded' build option in jabberd 2.3.1 does enable legacy (non-SASL) authentication. According to [1], the following entry is added in the 0.9.19 (release date 2011-12-21): Don't use SASL Authentication option for old servers [1] http://redmine.xabber.com/projects/1/wiki/History The xabber client from a friend in German language has the following option (in version 0.9.30b): SASL-Authentifizierung nutzen (empfohlen) Für sehr alte Server deaktivieren It seems that this option is somehow inverted, or miss-translated in xabber, as our findings would show what we have tested so far. My friend has reported this to the author of xabber, but did not hear anything back yet. Maybe you could also add this information (I guess you are also using xabber in German) to the bug report you already created. I do not know if maybe other clients (like yaxim you mention) share the same code base and those some of the same bugs. bye Fabian
Re: Cannot connect with android clients xabber or yaxim to jabberd2
On Monday 06 January 2014 22:06:32 Fabian Wenk wrote: Hello Guido On 06.01.2014 21:00, Guido Winkelmann wrote: For some reason, I cannot connect to jabberd2 2.3.1 with either xabber or yaxim. I originally thought this was a xabber bug, so I reported it here: https://github.com/redsolution/xabber-android/issues/268 However, it seems there are other people who suddenly have that problem after switching to jabberd2 2.3.1. Unfortunately, xabber does not display a useful error message, but yaxim says Session establishment not offered by server. A friend also had the problem with his xabber client connecting after he did upgrade jabberd from 2.2.17 to 2.3.1. After I have just discussed this issue with him again (as I did not had any problems, but I do not use it from Android), he pocked around in the settings and did deactivate the option (translated from German): use SASL authentication (recommended) (deactivate for very old servers) in xabber and he is able to connect again. You are right, if I disable SASL auth, I can login via xabber again. Guido
Re: Cannot connect with android clients xabber or yaxim to jabberd2
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
Re: Cannot connect with android clients xabber or yaxim to jabberd2
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? 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? 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. -- Tomasz Sterna:(){ :|:};: Instant Messaging ConsultantOpen Source Developer http://abadcafe.pl/ http://www.xiaoka.com/portfolio