view libpurple/plugins/mono/loader/debug-glue.c @ 30288:a81d44a11d99

If SASL authentication fails, we generally shouldn't be setting an error message, as the actual error was communicated via the "urn:ietf:params:xml:ns:xmpp-sasl" failure stanza. Setting an error means that jabber_auth_handle_failure() won't ever call jabber_parse_error() to extract the actual error message and interpretation. For example, if authentication fails, previously we would show "SASL authentication failed" and think it was a PURPLE_CONNECTION_ERROR_NETWORK_ERROR which is incorrect. Now, jabber_parse_error() gets a chance to return "Not Authorized", clear the saved password, and return PURPLE_CONNECTION_ERROR_AUTHENTICATION_FAILED. We should still set this error message if there is an internal SASL failure leading to SASL_BADPARAM or SASL_NOMEM.

#include "mono-glue.h"
#include "debug.h"

void purple_debug_glue(int type, MonoString *cat, MonoString *str)
{
	char *ccat;
	char *cstr;
	
	ccat = mono_string_to_utf8(cat);
	cstr = mono_string_to_utf8(str);
	
	purple_debug(type, ccat, "%s", cstr);
	
	g_free(ccat);
	g_free(cstr);
}