[Bug 1097366] Re: Pidgin client digest-uri checks fail with multiple virtual hosts

[Scott Moser]

@a7x,
  Thanks for your work on this bug, it looks like Mathieu is interested in getting it uploaded into raring, but needs you to help him out a little bit first.
  I'm marking this 'incomplete' for now, pending your response.  Please set it back to 'New' (or Confirmed) in raring after you've given the ejabberd.cnf that was requested.

** Changed in: ejabberd (Ubuntu Raring)
   Importance: Undecided => Medium

** Changed in: ejabberd (Ubuntu Raring)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1097366

Title:
  Pidgin client digest-uri checks fail with multiple virtual hosts

Status in “ejabberd” package in Ubuntu:
  Incomplete
Status in “ejabberd” source package in Precise:
  New
Status in “ejabberd” source package in Quantal:
  New
Status in “ejabberd” source package in Raring:
  Incomplete

Bug description:
  [Impact]

  Bug #1048634 fixes some Pidgin digest-uri check failures, but not all.
  There is another bug where Pidgin users won't be able to log in if
  there are multiple virtual hosts and the hostnames in the SRV records
  for the two XMPP hosts are different.

  This particular bug has already been fixed upstream:
  https://github.com/processone/ejabberd/commit/2bf8125abfeec9e1176ea7ab9793b8947f9c09b6
  as part of this upstream bug report:
  https://support.process-one.net/browse/EJAB-1578

  The upstream commit is not yet available in an official upstream
  release.  Presumably the patch will be included in ejabberd 2.1.12
  when it is released.

  This bug is known to affect precise, quantal, and raring.

  [Test Case]

  1. Put these lines in /etc/ejabberd/ejabberd.cfg:

      {hosts, ["example.com", "example.net"]}.
      {fqdn, "example.com"}.

  2. Configure DNS with the following example records:

      _xmpp-server._tcp.example.com. 86400 IN SRV 0 0 5269 xmpp.example.com.
      _xmpp-client._tcp.example.com. 86400 IN SRV 0 0 5222 xmpp.example.com.
      xmpp.example.com. 86400 IN A 127.0.0.1
      _xmpp-server._tcp.example.net. 86400 IN SRV 0 0 5269 xmpp.example.net.
      _xmpp-client._tcp.example.net. 86400 IN SRV 0 0 5222 xmpp.example.net.
      xmpp.example.net. 86400 IN CNAME xmpp.example.com.

     The above example records assume the ejabberd server and Pidgin
  client are both running on the same system (notice the 127.0.0.1).
  Change as appropriate.

  3. Create two ejabberd users:

     - example at example.com
     - example at example.net

  4. Configure Pidgin with both XMPP accounts

  With the patch, both accounts can successfully log in.  Without the
  patch, only the example at example.com account can log in because the
  example at example.net account will fail ejabberd's digest-uri checking
  logic.

  [Regression Potential]

  This change extends the syntax of the ejabberd config file.  Existing
  configuration files should remain compatible, but if there was a
  regression, it might manifest itself as an inability to correctly
  parse previously-valid configuration files.

  The change also affects the digest-uri checking logic.  A regression
  may result in users being unable to log in or overly permissive
  checks.

  The patch has been in the upstream repository since 2012-06-27, and I
  have been running it locally for almost as long without any problems.
  No subsequent changes to the affected region of code have been made
  upstream since this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1097366/+subscriptions