[kopete-bugs] [Bug 112213] XMPP Jabber TLS support

[kdebugs at mailinator.com]

https://bugs.kde.org/show_bug.cgi?id=112213


kdebugs at mailinator.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kdebugs at mailinator.com




--- Comment #20 from  <kdebugs mailinator com>  2009-04-21 22:56:30 ---
Yes, really annoying. I'd really like to see this bug fixed. This bug makes
kopete unusable to me and many other users of XMPP servers which use the
"STARTTLS" command. 

I cannot believe, it takes ages to fix this bug. This is what pidgin does:

T 192.168.2.10:42305 -> 192.168.40.6:5222 [AP]                                  
  <?xml version='1.0' ?>                                                        
##                                                                              
T 192.168.2.10:42305 -> 192.168.40.6:5222 [AP]                                  
  <stream:stream to='jabberhost.de' xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>                  
##                                                                              
T 192.168.40.6:5222 -> 192.168.2.10:42305 [AP]                                  
  <?xml version='1.0'?><stream:stream xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' id='105384129'
from='jabberhost.de' version='1.0'
   xml:lang='en'>                                                               
##                                                                              
T 192.168.40.6:5222 -> 192.168.2.10:42305 [AP]                                  
  <stream:features><starttls
xmlns='urn:ietf:params:xml:ns:xmpp-tls'><required/></starttls><mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism
  >PLAIN</mechanism></mechanisms><register
xmlns='http://jabber.org/features/iq-register'/></stream:features>              
##                                                                              
T 192.168.2.10:42305 -> 192.168.40.6:5222 [AP]                                  
  <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>                           
#                                                                               
T 192.168.40.6:5222 -> 192.168.2.10:42305 [AP]                                  
  <proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>    


and from beyond that point any conversation is cryptet by SSL - as required by
the server. But kopete instead doesn't seem even trying to start a
conversation:


T 192.168.2.10:49845 -> 192.168.40.6:5222 [AP]
  <?xml version="1.0"?>.<stream:stream
xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client"
to="jabberhost.de" >.
##
T 192.168.40.6:5222 -> 192.168.2.10:49845 [AP]
  <?xml version='1.0'?><stream:stream xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams' id='278883228'
from='jabberhost.de' xml:lang='en'
  ><stream:error><policy-violation
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text xml:lang=''
xmlns='urn:ietf:params:xml:ns:xmpp-streams'>Use of START
  TLS required</text></stream:error></stream:stream>
#####

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.