[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 deryni):

  * pending:  0 => 1

Comment:

 I have no idea why you brought discussion of TLS certificates into this,
 since that has no place here, the TLS connection is working fine (I assume
 since you are getting to failing authentication).

 No, setting xmpp.fqdn is not a hack (well it is, but not in the way you
 meant it). Without it the openfire server is unaware that the fqdn for the
 machine it lives on is different than the jid domain it is configured to
 serve. This causes problems with many sasl authentication mechanisms which
 need to know the specific entity they are authenticating with (for
 external authentication information, etc.).

 Look at ticket #5008 for another ticket on this.

 I will state again for clarity, I firmly believe given my reading of the
 digest-md5 sasl authentication rfc that what pidgin does now is correct
 and that previous behaviour was wrong. Feel free to find sources to
 dispute that if you want. Also, if you feel that the tls stuff is a
 problem or that pidgin is incorrectly using the fqdn somewhere other than
 what I indicated please include the snippet from the pidgin Debug Window
 to illustrate your point.

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