Code looks for an auth element below the returned streams:feature
authorTristan Hill <stan@saticed.me.uk>
Sun, 11 Oct 2009 18:26:24 +0200
changeset 608 59d517aa4770
parent 607 e2bd14357c9a
child 609 8dab2a5c2123
Code looks for an auth element below the returned streams:feature element which afaics from rfc3920 does not go here. This causes the connection to just hang. committer: Frank Zschockelt <lm@freakysoft.de>
loudmouth/lm-connection.c
--- a/loudmouth/lm-connection.c	Sun Oct 11 18:03:48 2009 +0200
+++ b/loudmouth/lm-connection.c	Sun Oct 11 18:26:24 2009 +0200
@@ -1081,7 +1081,6 @@
 {
     LmMessageNode *bind_node;
     LmMessageNode *starttls_node;
-    LmMessageNode *old_auth;
     LmMessageNode *sasl_mechanisms;
 
     starttls_node = lm_message_node_find_child (message->node, "starttls");
@@ -1153,10 +1152,8 @@
         }
     }
 
-    old_auth = lm_message_node_find_child (message->node, "auth");
-
     sasl_mechanisms = lm_message_node_find_child (message->node, "mechanisms");
-    if (connection->use_sasl && old_auth != NULL && sasl_mechanisms == NULL) {
+    if (connection->use_sasl && sasl_mechanisms == NULL) {
         g_log (LM_LOG_DOMAIN, LM_LOG_LEVEL_SASL,
                "Server uses XEP-0078 (jabber iq auth) instead of SASL\n");
         /* So the server is XMPP1.0, but doesn't support SASL and uses