[Pidgin] #17059: broken sasl after 2.10.11 version

Pidgin trac at pidgin.im
Sat Jul 2 19:27:29 EDT 2016


#17059: broken sasl after 2.10.11 version
------------------------------+--------------------------
 Reporter:  pidginuser_again  |      Owner:  EionRobb
     Type:  patch             |     Status:  new
Milestone:  2.11.1            |  Component:  unclassified
  Version:  2.10.12           |   Keywords:
------------------------------+--------------------------
 Hello, I use pidgin as an xmpp client with sso (gssapi over mit kerberos)
 in windows environment with Openfire 3.9.1 server.
 With < 2.10.11 version of pidgin I have following debug output:
 {{{
 .....
 certificate: Successfully verified certificate for jabber.domain.com
 (01:23:25) jabber: Sending (ssl) (user at domain.com/work): <stream:stream
 to='domain.com' xmlns='jabber:client'
 xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
 (01:23:25) jabber: Recv (ssl)(453): <?xml version='1.0'
 encoding='UTF-8'?><stream:stream
 xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client"
 from="domain.com" id="2fb6e513" xml:lang="en"
 version="1.0"><stream:features><mechanisms xmlns="urn:ietf:params:xml:ns
 :xmpp-sasl"><mechanism>GSSAPI</mechanism></mechanisms><compression
 xmlns="http://jabber.org/features/compress"><method>zlib</method></compression><auth
 xmlns="http://jabber.org/features/iq-auth"/></stream:features>
 (01:23:25) sasl: Mechs found: GSSAPI
 (01:23:25) jabber: Sending (ssl) (user at domain.com/work): <auth
 xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='GSSAPI'
 ........
 }}}
 And everything is fine.

 But with 2.10.12 and 2.11.0 versions I have the following
 {{{
 ...
 certificate: Successfully verified certificate for jabber.domain.com
 (01:26:28) jabber: Sending (ssl) (user at domain.com/work): <stream:stream
 to='domain.com' xmlns='jabber:client'
 xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
 (01:26:28) jabber: Recv (ssl)(453): <?xml version='1.0'
 encoding='UTF-8'?><stream:stream
 xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client"
 from="domain.com" id="27bf41fd" xml:lang="en"
 version="1.0"><stream:features><mechanisms xmlns="urn:ietf:params:xml:ns
 :xmpp-sasl"><mechanism>GSSAPI</mechanism></mechanisms><compression
 xmlns="http://jabber.org/features/compress"><method>zlib</method></compression><auth
 xmlns="http://jabber.org/features/iq-auth"/></stream:features>
 (01:26:28) sasl: Mechs found: GSSAPI
 (01:26:28) sasl: No worthy mechs found
 (01:26:30) account: Disconnecting account user at domain.com/work (02663418)
 (01:26:30) connection: Disconnecting connection 04A68ED8
 (01:26:30) jabber: Sending (ssl) (user at domain.com/work): </stream:stream>
 (01:26:30) connection: Destroying connection 04A68ED8
 ...
 }}}

 P.S: Windows 7 x64 professional + Mit kerberos 4.x (non admin domain
 account with UAC enabled)

 I think it has something to do with Cyrus SASL library update.

--
Ticket URL: <https://developer.pidgin.im/ticket/17059>
Pidgin <https://pidgin.im>
Pidgin


More information about the Tracker mailing list