[Pidgin] #5729: unable to XMPP-login by using PLAIN mechanism over unencrypted streams

Pidgin trac at pidgin.im
Tue May 6 13:35:59 EDT 2008


#5729: unable to XMPP-login by using PLAIN mechanism over unencrypted streams
-----------------------+----------------------------------------------------
  Reporter:  calessio  |       Owner:  nwalp
      Type:  defect    |      Status:  new  
  Priority:  minor     |   Milestone:       
 Component:  XMPP      |     Version:  2.4.1
Resolution:            |    Keywords:       
   Pending:  1         |  
-----------------------+----------------------------------------------------
Changes (by datallah):

  * pending:  0 => 1

Old description:

> I'm trying to use pidgin 2.4.1 to login on a server which allows PLAIN
> mechanism over unencrypted streams, but pidgin is unable to login and
> remains in the "connecting" status forever.
> I tried another XMPP client (Exodus) and it works fine.
> The difference between the two client, looking at the server-side logs,
> is that pidgin does not send the "mechanism PLAIN" SASL command, the
> other client does.
>
> Here is the server log generated when connecting with PIDGIN:
>
> ClientSession[null] packetTransferred, sent: <features
> xmlns='http://etherx.jabber.org/streams'><mechanisms
> xmlns='urn:ietf:params:xml:ns:xmpp-
> sasl'><mechanism>PLAIN</mechanism></mechanisms></features>
> ...
> ClientSession started process()
> Session[null] processing input
> Session[null] processing request
> [ClientPacketDispatcher] SASLPacket detected
> [Sasl] new packet
> [Sasl] ptype=null
> [Sasl] act = {urn:ietf:params:xml:ns:xmpp-sasl}auth
> [Sasl] data = [B at 1ac3cb6
> [Sasl] elemLst size = 0
> [Sasl] IS SASLAuthPacket
> [Sasl] mechanism
> [Sasl] action is AUTHENTICATE
> [Sasl] unsupported mechanism
> ...
>
> Here is the server log generated when connecting with EXODUS:
>
> ClientSession[null] packetTransferred, sent: <features
> xmlns='http://etherx.jabber.org/streams'><mechanisms
> xmlns='urn:ietf:params:xml:ns:xmpp-
> sasl'><mechanism>PLAIN</mechanism></mechanisms></features>
> ...
> ClientSession started process()
> Session[null] processing input
> Session[null] processing request
> [ClientPacketDispatcher] SASLPacket detected
> [Sasl] new packet
> [Sasl] ptype=null
> [Sasl] act = {urn:ietf:params:xml:ns:xmpp-sasl}auth
> [Sasl] data = [B at 187cde8
> [Sasl] elemLst size = 0
> [Sasl] IS SASLAuthPacket
> --> [Sasl] mechanism PLAIN <-- this is missing with PIDGIN!
> [Sasl] action is AUTHENTICATE
> [Sasl] PLAIN mechanism requested
> [Sasl] authzid = uid at mydomain
> [LDAP] Authenticating user uid
> ...

New description:

 I'm trying to use pidgin 2.4.1 to login on a server which allows PLAIN
 mechanism over unencrypted streams, but pidgin is unable to login and
 remains in the "connecting" status forever.
 I tried another XMPP client (Exodus) and it works fine.
 The difference between the two client, looking at the server-side logs, is
 that pidgin does not send the "mechanism PLAIN" SASL command, the other
 client does.

 Here is the server log generated when connecting with PIDGIN:
 {{{
 ClientSession[null] packetTransferred, sent: <features
 xmlns='http://etherx.jabber.org/streams'><mechanisms
 xmlns='urn:ietf:params:xml:ns:xmpp-
 sasl'><mechanism>PLAIN</mechanism></mechanisms></features>
 ...
 ClientSession started process()
 Session[null] processing input
 Session[null] processing request
 [ClientPacketDispatcher] SASLPacket detected
 [Sasl] new packet
 [Sasl] ptype=null
 [Sasl] act = {urn:ietf:params:xml:ns:xmpp-sasl}auth
 [Sasl] data = [B at 1ac3cb6
 [Sasl] elemLst size = 0
 [Sasl] IS SASLAuthPacket
 [Sasl] mechanism
 [Sasl] action is AUTHENTICATE
 [Sasl] unsupported mechanism
 ...
 }}}

 Here is the server log generated when connecting with EXODUS:
 {{{
 ClientSession[null] packetTransferred, sent: <features
 xmlns='http://etherx.jabber.org/streams'><mechanisms
 xmlns='urn:ietf:params:xml:ns:xmpp-
 sasl'><mechanism>PLAIN</mechanism></mechanisms></features>
 ...
 ClientSession started process()
 Session[null] processing input
 Session[null] processing request
 [ClientPacketDispatcher] SASLPacket detected
 [Sasl] new packet
 [Sasl] ptype=null
 [Sasl] act = {urn:ietf:params:xml:ns:xmpp-sasl}auth
 [Sasl] data = [B at 187cde8
 [Sasl] elemLst size = 0
 [Sasl] IS SASLAuthPacket
 --> [Sasl] mechanism PLAIN <-- this is missing with PIDGIN!
 [Sasl] action is AUTHENTICATE
 [Sasl] PLAIN mechanism requested
 [Sasl] authzid = uid at mydomain
 [LDAP] Authenticating user uid
 ...
 }}}

Comment:

 Please also include the [TipsForBugReports Pidgin debug output].

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


More information about the Tracker mailing list