[Pidgin] #5161: Pidgin sends the wrong domain to Jabber server

[Pidgin]

#5161: Pidgin sends the wrong domain to Jabber server
-----------------------+----------------------------------------------------
  Reporter:  unacoder  |       Owner:  nwalp
      Type:  defect    |      Status:  new  
  Priority:  minor     |   Milestone:       
 Component:  XMPP      |     Version:  2.4.0
Resolution:            |    Keywords:       
   Pending:  1         |  
-----------------------+----------------------------------------------------
Changes (by unacoder):

  * pending:  1 => 0

Comment:

 > In what part of the authentication is pidgin sending the fqdn of your
 server?

 This was not really apparent due to poor server logs

 > Do you have the fqdn input in pidgin as the Connect Server?

 No, we're using the xmpp+client SRV record to locate the server

 > The reason your build from source works is because you didn't build with
 Cyrus SASL support.

 Why is the FQDN for certificate exchange difference between SASL and TLS?

 > If you are using Openfire you need to add the xmpp.fqdn property to
 Openfire with the fqdn of your host.

 We are;

 This worked around the problem, but this is a hack.  The server's
 certificate domain should be the "virtual host", not the real hostname of
 the server.  In a distributed https environment wwwX.domain.tld would use
 www.domain.tld's certificate, why is this any different?

 -Dan

-- 
Ticket URL: <http://developer.pidgin.im/ticket/5161#comment:3>
Pidgin <http://pidgin.im>
Pidgin