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

[Ubuntu Foundations Team Bug Bot]

The attachment "debdiff for precise" of this bug report has been
identified as being a patch in the form of a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  In the event that this is in
fact not a patch you can resolve this situation by removing the tag
'patch' from the bug report and editing the attachment so that it is not
flagged as a patch.  Additionally, if you are member of the ubuntu-
sponsors team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by
Brian Murray.  Please contact him regarding any issues with the action
taken in this bug report.]

-- 
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:
  New

Bug description:
  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.

  For example, suppose ejabberd.cnf contains:

  {hosts, ["foo.example", "bar.example"]}.
  {fqdn, "xmpp.foo.example"}.

  and DNS lookups return the following:

  dig -t SRV _xmpp-client._tcp.foo.example. -> xmpp.foo.example:5222
  dig -t SRV _xmpp-client._tcp.bar.example. -> xmpp.bar.example:5222
  dig -t A xmpp.foo.example. -> 192.0.2.123
  dig -t A xmpp.bar.example. -> 192.0.2.123

  then Pidgin clients with *@bar.example Jabber IDs are NOT able to log
  in. The digest-uri sent by these clients – "xmpp/xmpp.bar.example" –
  doesn't pass ejabberd's digest-uri checking logic. Pidgin clients with
  *@foo.example Jabber IDs do work, however.

  This particular bug has already been fixed upstream:
  https://github.com/processone/ejabberd/commit/2bf8125abfeec9e1176ea7ab9793b8947f9c09b6

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