#139: c2s gsasl mio crash
-------------------+--------------------------------------------------------
Reporter: tofu | Owner: smoku
Type: defect | Status: closed
Priority: major | Component: c2s
Version: 2.1.14 | Resolution: fixed
Keywords: | Tracforge_linkmap:
Blocking: |
-------------------+--------------------------------------------------------
Comment (by tofu):
I have not gotten it to fail, which is great! In sasl_gsasl.c you removed
the following at line 354.
{{{
354 if(ret != GSASL_OK && ret != GSASL_NEEDS_MORE) {
355 _sx_debug(ZONE, "gsasl_step failed, no sasl
for this conn; (%d): %s", ret, gsasl_strerror(ret));
356 _sx_nad_write(s, _sx_sasl_failure(s,
_sasl_err_MALFORMED_REQUEST), 0);
357 if(out != NULL) free(out);
358 if(buf != NULL) free(buf);
359 return;
360 }
}}}
I was just wondering why and wouldnt it create problems if gsasl_step did
fail?
--
Ticket URL: <http://jabberd2.xiaoka.com/ticket/139#comment:7>
jabberd2 <http://jabberd2.xiaoka.com/>
versatile XMPP server
_______________________________________________
Jabberd2 mailing list
[email protected]
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
