XMPP, Server does not use any supported authentication method

Alexander Ustinov ustinov at physics.spbstu.ru
Mon Sep 12 01:22:30 EDT 2011


> In no particular order:
>     * What are the contents of /etc/hosts and /etc/hostname?
>     * Which exact version of Cyrus SASL is installed (`apt-cache policy
> libsasl2-modules`)
>     * If you upgrade to the Cyrus SASL from Debian Unstable, does it work?

3. It doesn't.
2. Output is after i tried 3.

I have not mentioned before that this situation is on two computers, 
both running debian testing. One i386, one amd64.

> # echo /etc/hosts: && cat /etc/hosts && echo /etc/hostname: && cat 
> /etc/hostname
> /etc/hosts:
> 127.0.0.1 localhost
> 127.0.1.1 blower.emission blower.emission
>
> # The following lines are desirable for IPv6 capable hosts
> ::1 ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
> /etc/hostname:
> blower

> #apt-cache policy libsasl2-modules
> libsasl2-modules:
>   Установлен (Installed): 2.1.24~rc1.dfsg1+cvs2011-05-23-6
>   Кандидат (Candidate):   2.1.24~rc1.dfsg1+cvs2011-05-23-6
>   Таблица версий (Version table):
>  *** 2.1.24~rc1.dfsg1+cvs2011-05-23-6 0
>         100 /var/lib/dpkg/status
>      2.1.24~rc1.dfsg1+cvs2011-05-23-4 0
>         500 http://194.85.96.211/debian/ testing/main i386 Packages


> It may come down to your needing to install the Cyrus SASL debug symbols
> and start bisecting sasl_client_new() with breakpoints until we can figure
> out what is actually returning SASL_FAIL (-1) (or adding breakpoints to
> every SASL_FAIL return in Cyrus SASL and seeing which one hits).
Never tried such things before. :) Will try to do my best.





More information about the Support mailing list