* Konstantin Khomoutov [2012-06-14 17:12 +0200]:
On Thu, 14 Jun 2012 11:18:01 +0200
Nicolas Évrard <ni...@no-log.org> wrote:

* Konstantin Khomoutov  [2012-06-13 22:55 +0200]:
>On Wed, Jun 13, 2012 at 08:22:47PM +0200, Nicolas Évrard wrote:
>
>> Package: ejabberd
>> Followup-For: Bug #654853
>>
>> Dear Maintainer,
>>
>> We installed the new version of ejabberd on our server but
>> unfortunately I still can not authenticate.
>[...]
>
>Can you please be more precise about "the new version of ejabberd"?
>
>This bug has been fixed upstream in 2.1.11 which is currently
>pending an upload (Gerfried told me the upload has chances to happen
>this weekend) hence if you installed a new version you either built
>it from the upstream tarball or installed in using their binary
>installer or installed a not-so-recent version.  In the former two
>cases please comment in the upstream BTS, in the latter please wait
>for the prospective upload.

I am using minbiff to connect to a ejabberd hosted on a gentoo server.
The running version there is 2.1.11 and unless you patch the said file
I am afraid that the bug is also present in debian.

Well, I've just installed Pidgin on my desktop Windows machine
and connected to an ejabberd 2.11.1-1 instance installed into a Sid
sandbox.  The Pidgin version is

Pidgin 2.10.4 (libpurple 2.10.4)
03f3e779309e683d092706d76a5253c6794d3a66

I am also using this version:

balisto:~% pidgin --version
Pidgin 2.10.4 (libpurple 2.10.4)


… snip …

I have one "host" (XMPP domain) in my ejabberd configuration --
"localhost".
The real host name of the machine which runs the sandbox is
jukebox.domain007.com (don't ask why it is what it is), and I have
configured it in my Pidgin config as the server to connect to (so no
SRV lookups are performed).

As you can see, I have successfully authenticated as "kostix@localhost"
using DIGEST-MD5 after upgrading the session to use TLS.

So, to me the issue appears to be either fixed or non-existing.
Is there something in my setup (XMPP domain? server hostname?
client settings?) that prevents the issue being discussed form
exposing itself?

From my debugging session in the ejabber the URI problem is solved.
Maybe I should make another bug (but before I'll wait for the ejabberd
upload to get the fixed version).

--
(°> Nicolas Évrard
( ) Liège
 `¯

Attachment: signature.asc
Description: Digital signature

Reply via email to