Changeset 88591fd


Ignore:
Timestamp:
2006-10-01T16:15:46Z (14 years ago)
Author:
Wilmer van der Gaast <wilmer@…>
Branches:
master
Children:
c1ed6527
Parents:
0e2d97f
Message:

Better fix for servers that report to comply with XMPP 1.0 but don't offer
SASL authentication options. Previous fix tried to do IQ authentication
even after successful SASL authentications.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • protocols/jabber/io.c

    r0e2d97f r88591fd  
    305305                        return XT_ABORT;
    306306        }
    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;
     307        /* If the server *SEEMS* to support SASL authentication but doesn't
     308           support it after all, we should try to do authentication the
     309           other way. jabber.com doesn't seem to do SASL while it pretends
     310           to be XMPP 1.0 compliant! */
     311        else if( !( jd->flags & JFLAG_AUTHENTICATED ) && sasl_supported( gc ) )
     312        {
     313                if( !jabber_start_iq_auth( gc ) )
     314                        return XT_ABORT;
    316315        }
    317316       
Note: See TracChangeset for help on using the changeset viewer.