8 commits

Author	SHA1	Message	Date
LemonBoy	24d32c28ee	Don't handle 908 as a critical failure ... "if the mechanism is unknown, 908 is optional, 904 (or equivalent error condition) is required"	2015-09-11 23:21:33 +02:00
LemonBoy	49c4ea5fd9	Parse the error string received by the server ... So that in case of SASL failure the user sees a nice error message.	2015-09-11 23:20:07 +02:00
LemonBoy	1f114d75c6	Consider the SASL handshake successful on 903	2015-09-11 23:17:46 +02:00
LemonBoy	55387dd93d	Handle event 906 and 908	2015-09-11 22:23:38 +02:00
LemonBoy	6645d0d38d	Explicitly set the authorization id during the PLAIN handshake ... On error show the user the message sent by the server.	2015-09-11 22:09:47 +02:00
LemonBoy	171b67441d	Replace spaces with tabs	2015-09-11 01:17:18 +02:00
LemonBoy	c90c7deac3	Address all the points outlined in the first review ... Replace G_SOURCE_REMOVE with FALSE for the compatibility sake. Zero the timeout id after g_source_remove and when exipred. Save the sasl_* options in sig_chatnet_saved().	2015-09-11 01:07:43 +02:00
LemonBoy	b8d3301d34	SASL support ... The only supported methods are PLAIN and EXTERNAL, the latter is untested as of now. The code gets the values from the keys named sasl_{mechanism,username,password} specified for each chatnet.	2015-09-11 00:30:16 +02:00