Changeset 501b4e0


Ignore:
Timestamp:
2006-10-02T16:42:32Z (13 years ago)
Author:
Wilmer van der Gaast <wilmer@…>
Branches:
master
Children:
995913b
Parents:
d9282b4
Message:

Added a useful error message for SASL negotiation failures and turned off
the little hack in jabber_write() for now because it breaks error handling.

Location:
protocols/jabber
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • protocols/jabber/io.c

    rd9282b4 r501b4e0  
    5252                   it via the event handler. If not, add the handler. (In
    5353                   most cases it probably won't be necessary.) */
     54                /* Disabling this trick for now because there's really not
     55                   a good way to catch errors yet. :-(
    5456                if( jabber_write_callback( gc, jd->fd, GAIM_INPUT_WRITE ) )
     57                */
    5558                        jd->w_inpa = b_input_add( jd->fd, GAIM_INPUT_WRITE, jabber_write_callback, gc );
    5659        }
     
    6467        }
    6568       
    66         /* FIXME: write_callback could've generated a real error! */
     69        /* FIXME: write_callback could've generated a real error! Have to
     70           find a way to find out if we have to return 0 here. Looking for
     71           ourselves in the linked list of connections is a possibility,
     72           but it'd be too time-consuming... */
    6773        return 1;
    6874}
  • protocols/jabber/sasl.c

    rd9282b4 r501b4e0  
    6464        if( !sup_plain && !sup_digest )
    6565        {
     66                hide_login_progress( gc, "No known SASL authentication schemes supported" );
    6667                signoff( gc );
    6768                return XT_ABORT;
Note: See TracChangeset for help on using the changeset viewer.