From 403e02ecfc87ec2b68b8d3e4012ed6ca0910c74f Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sun, 21 Jul 2013 02:55:36 +0000 Subject: [PATCH] Added a comment --- ..._2d311f520aee04287df6bddfd8535734._comment | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 doc/bugs/cannot_connect_to_xmpp_server/comment_5_2d311f520aee04287df6bddfd8535734._comment diff --git a/doc/bugs/cannot_connect_to_xmpp_server/comment_5_2d311f520aee04287df6bddfd8535734._comment b/doc/bugs/cannot_connect_to_xmpp_server/comment_5_2d311f520aee04287df6bddfd8535734._comment new file mode 100644 index 0000000000..62e0389412 --- /dev/null +++ b/doc/bugs/cannot_connect_to_xmpp_server/comment_5_2d311f520aee04287df6bddfd8535734._comment @@ -0,0 +1,28 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.0.140" + subject="comment 5" + date="2013-07-21T02:55:36Z" + content=""" +Great. We can see git-annex opens the XMPP stream tag, and your server responds by opening its own tag. + +Compare with this similar conversation: + + joey@gnu:~>telnet kite 5222 + Trying 80.68.85.49... + Connected to wren.kitenet.net. + Escape character is '^]'. + + + + +So far it's the same as the conversation with your server, but now my server goes on to send another line: + + SCRAM-SHA-1DIGEST-MD5 + +While your server does not send anything. + +I see that my XMPP client library expects to receive a features tag at this point. Until it does, it won't continue. It may be that your server is not sending the features because it does not implement TLS or any of the other features that need to be advertised. + +I think I need to report this to the author of the XMPP client library. It would help to know what XMPP server software you're using, and if it has TLS support enabled. +"""]]