Login issue with Pidgin using SRV records

Bug #1048634 reported by Milan on 2012-09-10
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ejabberd (Debian)
Fix Released
ejabberd (Ubuntu)
Adrien Cunin

Bug Description

= Original report =

The problem has been discussed and fixed in these Debian and upstream bugs:



I am affected by this bug on 12.04 with ejabberd 2.1.10-2ubuntu1. Can you update the Ubuntu package on 12.04?

= Precise SRU =


This bug impacts at least Pidgin users, as they are unable to connect to affected ejabberd servers. The problem appears when Pidgin uses SRV records to find the server.

[Test Case]

 * Try connecting to the ejabberd server using Pidgin. Pidgin returns a "not authorized" error.
 * Update ejabber package to 2.1.10-2ubuntu1.1.
 * Try connecting again. No error appears and you are successfully connected.

[Regression Potential]

The patch concerns a part of the code responsible for connection handling. However, it has been included upstream for several months, and has been in Debian since August.

Changed in ejabberd (Debian):
status: Unknown → Fix Released
Logan Rosen (logan) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Quantal Quetzal.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

Changed in ejabberd (Ubuntu):
status: New → Fix Released
Adrien Cunin (adri2000) on 2012-12-19
Changed in ejabberd (Ubuntu):
importance: Undecided → Medium
Changed in ejabberd (Ubuntu Precise):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Adrien Cunin (adri2000)
Adrien Cunin (adri2000) on 2012-12-19
description: updated
summary: - No login possible at ejabberd with libpurple and vhost
+ Login issue with Pidgin using SRV records
Adrien Cunin (adri2000) wrote :

2.1.10-2ubuntu1.1 waiting to be approved into precise-proposed.

Hello Milan, or anyone else affected,

Accepted ejabberd into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ejabberd/2.1.10-2ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in ejabberd (Ubuntu Precise):
status: In Progress → Fix Committed
tags: added: verification-needed
Milan (public-mjh) wrote :

Short version: I tested the new package and it fixes the bug. I will change the tag.

Adrien, thanks for creating the package and completing my initial bug report! Colin, thanks for the advice.

This is what I did in detail:

I reproduced the bug with ejabberd=2.1.10-2ubuntu1 (current precise version) and Pidgin 2.10.6.

(Setup: jabber server with virtual hosts jabber.example.com and jabber.example.org. jabber.example.com SRV sends the XMPP client to jabber.example.com. jabber.example.org SRV sends the client to jabber.othername.com. Both jabber.example.com and jabber.othername.com go to the same jabber server.

The bug was: Login with pidgin is possible for jabber.example.com, but not for jabber.example.org.)

Then I installed ejabberd=2.1.10-2ubuntu1.1 from precise-testing. Login is now also possible for jabber.example.org if the newly introduced "fqdn" setting matches the SRV record (here: jabber.othername.com). As far as I can see, this is how the patch is supposed to work (cf. https://support.process-one.net/browse/EJAB-1529). Therefore, the bug is fixed by the new package.
(The default value of the "fqdn" setting is the system hostname(1), which did not match jabber.othername.com in my case.)

I did the following tests for regressions:

Login to jabber.example.com (to which login was possible previously) works as before. It is not affected by the value of the new "fqdn" setting.

Interaction with other Jabber servers (gmail.com, gmx.de) works as before.

tags: added: verification-done
removed: verification-needed

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ejabberd - 2.1.10-2ubuntu1.1

ejabberd (2.1.10-2ubuntu1.1) precise-proposed; urgency=low

  * Backported debian/patches/relax-digest-uri-handling.patch from 2.1.10-3
     - Fixes a problem with Pidgin not being able to log in on a server using
       SRV records (LP: #1048634)
 -- Adrien Cunin <email address hidden> Wed, 19 Dec 2012 14:41:57 +0100

Changed in ejabberd (Ubuntu Precise):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.