irssi - The client of the future

Age	Commit message (Collapse)	Author
2018-02-02	do not reuse sasl timeout	ailin-nemui

2017-11-30	fix comments	ailin-nemui

2017-01-24	Prevent a memory leak during the processing of the SASL response.	LemonBoy
	We also get rid of an allocation in the process of doing so.
2016-12-12	Add an option to stop the connection when SASL fails.	LemonBoy

2016-08-29	SASL: handle fragmentation	Kenny Root
	The IRCv3 SASL extension says that AUTHENTICATION payloads of exactly 400 bytes in length indicate that the message is fragmented and will continue in a subsequent message. Handle the reassembly and splitting of these messages so that we are compliant with the specification.
2016-06-01	Correct the name of the emitted signal.	LemonBoy
	There's a typo in 'sasl_fail', the signal that's emitted should be 'server sasl failure' and not 'server sasl fail'.
2016-03-20	Use 0 as a sentinel value for sasl_timeout	LemonBoy
	If sasl_timeout is never initialized with a valid timeout id then calling /disconnect on the server calls g_source_remove() with 0 as tag, causing an harmless error message to be printed. Beside that, the sasl_timeout field is defined as a unsigned int. We can use 0 as sentiel since g_timeout_add returns tags that are always greater than zero.
2016-03-11	Remove sasl timeout source when the server disconnects	dequis

2016-03-08	Fix SASL EXTERNAL authentication	Mantas Mikulėnas
	The "AUTHENTICATE" command is always required – it's part of the IRCv3 SASL framing. RFC 4422 only documents the Base64 payload.
2015-09-21	Use formats instead of g_warning	LemonBoy
	Add some copyright headers here and there too.
2015-09-11	Don't handle 908 as a critical failure	LemonBoy
	"if the mechanism is unknown, 908 is optional, 904 (or equivalent error condition) is required"
2015-09-11	Parse the error string received by the server	LemonBoy
	So that in case of SASL failure the user sees a nice error message.
2015-09-11	Consider the SASL handshake successful on 903	LemonBoy

2015-09-11	Handle event 906 and 908	LemonBoy

2015-09-11	Explicitly set the authorization id during the PLAIN handshake	LemonBoy
	On error show the user the message sent by the server.
2015-09-11	Replace spaces with tabs	LemonBoy

2015-09-11	Address all the points outlined in the first review	LemonBoy
	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	SASL support	LemonBoy
	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.