Ignore:
Timestamp:
2006-10-01T09:40:55Z (18 years ago)
Author:
Wilmer van der Gaast <wilmer@…>
Branches:
master
Children:
88591fd
Parents:
6baca2a
Message:

Can now log in to the jabber.com server (which pretends to support XMPP 1.0
but does NOT (seem to) support SASL authentication).

File:
1 edited

Legend:

Unmodified
Added
Removed
  • protocols/jabber/io.c

    r6baca2a r0e2d97f  
    301301           properly before we attempt SASL authentication. */
    302302        if( ( c = xt_find_node( node->children, "mechanisms" ) ) )
     303        {
    303304                if( sasl_pkt_mechanisms( c, data ) == XT_ABORT )
    304305                        return XT_ABORT;
     306        }
     307        else
     308        {
     309                /* If the server *SEEMS* to support SASL authentication but
     310                   doesn't support it after all, we should try to do
     311                   authentication the other way. jabber.com doesn't seem to
     312                   do SASL while it pretends to be XMPP 1.0 compliant! */
     313                if( sasl_supported( gc ) )
     314                        if( !jabber_start_iq_auth( gc ) )
     315                                return XT_ABORT;
     316        }
    305317       
    306318        if( ( c = xt_find_node( node->children, "bind" ) ) )
Note: See TracChangeset for help on using the changeset viewer.