[Bug 1097366] Re: Pidgin client digest-uri checks fail with multiple virtual hosts
a7x
1097366 at bugs.launchpad.net
Tue Feb 5 16:13:01 UTC 2013
It has not yet been fixed in Raring. Precise, Quantal, and Raring are
all at 2.1.10, so the attached upstream patch should apply cleanly to
Raring.
I will edit the bug description according to the SRU procedure.
--
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
More information about the Ubuntu-sponsors
mailing list