comparison: libpurple/protocols/jabber/auth_cyrus.c
libpurple/protocols/jabber/auth_cyrus.c
- branch
- cpw.darkrain42.xmpp.scram
- changeset 28861
- b77599fa1e36
- parent 28860
- d2a057cdd7b6
- child 29008
- 1f288722b5cd
equal
deleted
inserted
replaced
| 28860:d2a057cdd7b6 | 28861:b77599fa1e36 |
|---|---|
| 254 * Note: xep-0078 points out that using jabber:iq:auth after a sasl failure is wrong. However, | 254 * Note: xep-0078 points out that using jabber:iq:auth after a sasl failure is wrong. However, |
| 255 * I believe this refers to actual authentication failure, not a simple lack of concordant mechanisms. | 255 * I believe this refers to actual authentication failure, not a simple lack of concordant mechanisms. |
| 256 * Doing otherwise means that simply compiling with SASL support renders the client unable to connect to servers | 256 * Doing otherwise means that simply compiling with SASL support renders the client unable to connect to servers |
| 257 * which would connect without issue otherwise. -evands | 257 * which would connect without issue otherwise. -evands |
| 258 */ | 258 */ |
| 259 js->auth_mech = NULL; | |
| 259 jabber_auth_start_old(js); | 260 jabber_auth_start_old(js); |
| 260 return NULL; | 261 return NULL; |
| 261 } | 262 } |
| 262 /* not reached */ | 263 /* not reached */ |
| 263 break; | 264 break; |
