[kopete-bugs] [Bug 241716] New: Kopete uses old style XMPP authentication

Alex Cartwright alexc223 at googlemail.com
Mon Jun 14 12:15:03 CEST 2010


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

           Summary: Kopete uses old style XMPP authentication
           Product: kopete
           Version: 1.00
          Platform: Archlinux Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Jabber Plugin
        AssignedTo: kopete-bugs at kde.org
        ReportedBy: alexc223 at googlemail.com


Version:           1.00 (using KDE 4.4.3) 
OS:                Linux

After setting up an XMPP server using Prosody (http://prosody.im) and not using
SSL/TLS we had some issues connecting via Kopete. This is the debug logs from
Prosody:

Jun 14 10:09:04 socket  debug   server.lua: accepted new client connection from
192.168.0.19:42681 to 5222
Jun 14 10:09:04 sessionmanager  debug   open sessions now: 6
Jun 14 10:09:04 c2s742640       debug   Client sent opening <stream:stream> to
example.com
Jun 14 10:09:04 c2s742640       debug   Sent reply <stream:stream> to client
Jun 14 10:09:04 c2s742640       debug   Received[c2s_unauthed]: <iq id='auth_1'
type='get' to='example.com'>
Jun 14 10:09:04 modulemanager   debug   Stanza of type iq from c2s_unauthed has
xmlns: jabber:iq:auth
Jun 14 10:09:04 modulemanager   debug   Unhandled c2s_unauthed stanza: iq;
xmlns=jabber:iq:auth
Jun 14 10:09:04 socket  debug   server.lua: client 192.168.0.19:42681 read
error: closed
Jun 14 10:09:04 socket  debug   server.lua: closed client handler and removed
socket from list

After talking with others in the Prosody community, I had to enable the
'legacyauth' module which suggests that Kopete is using an old style XMPP
authentication which is not what RFC3920 (http://www.ietf.org/rfc/rfc3920.txt)
specifies.

A modern client such as Kopete should not have to rely on legacy
authentication. 


Reproducible: Always

Steps to Reproduce:
Setup a Prosody server and disable SSL/TLS. Ensure the 'legacyauth' module is
disabled and attempt to connect to the server via Kopete.

Actual Results:  
Kopete instantly connects and then disconnects

Expected Results:  
Successful connection to the server

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


More information about the kopete-bugs mailing list