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

 I don't have intimate knowledge of either SASL or TLS, and I'm sure you
 know the protocols much better than I do.  I was probably making a bad
 comparison.

 > 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).

 I was just bringing up that TLS '''is''' functioning, and I was assuming
 that if that was true, then pidgin must not be sending the server FQDN
 during the handshake process.  Like I said before though, I'm not
 intimately familiar with the protocol, so this is a moot point and a bad
 argument.  sorry.

 > 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

 That makes sense as the domain name of the jabber server is a virtual host
 for the server, and doesn't match the real hostname on the box.  Openfire
 would have no way of determining that..

 So what it really boils down to is that, if you're not using the real
 hostname of the server, you have to tell openfire what the fdqn is that a
 jabber client will expect the server to be using...

 My mistake.  Keep up the good work guys, great IM client!

 -Dan

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