diff libpurple/protocols/jabber/jabber.h @ 22640:23fe481afccf

The next version of RFC 3920, the draft of which can be found at http://www.xmpp.org/internet-drafts/draft-saintandre-rfc3920bis-04.html, and subsequent email clarifications with Peter Saint-Andre and Alexey Melnikov indicate that we should be trying the next mechanism in line after one mechanism fails. We should also be ensuring that the mech list is sorted in order of descending security, which we don't do yet; however, servers are supposed to send us a sorted list, as well, so this isn't a major issue. committer: Evan Schoenberg <evan.s@dreskin.net>
author Stu Tomlinson <stu@nosnilmot.com>
date Sun, 13 Apr 2008 06:37:47 +0000
parents d63892ade0a6
children aaaff38e144f 224169be5830 26eabe8e739b 69d54f84350a
line wrap: on
line diff
--- a/libpurple/protocols/jabber/jabber.h	Sat Apr 12 23:34:27 2008 +0000
+++ b/libpurple/protocols/jabber/jabber.h	Sun Apr 13 06:37:47 2008 +0000
@@ -158,6 +158,11 @@
 	void *sasl;
 	void *sasl_cb;
 #endif
+	/* did someone say something about the end of the struct? */
+#ifdef HAVE_CYRUS_SASL
+	const char *current_mech;
+	int auth_fail_count;
+#endif
 
 	int sasl_state;
 	int sasl_maxbuf;