From 3348f5d05382c23fd9ba884646c0f193f3f94681 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 12 Apr 2013 22:25:13 +0000 Subject: [PATCH] Added a comment --- ...comment_3_1a7ff955e9173f13d10b75f203792384._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/XMPP_authentication_failure/comment_3_1a7ff955e9173f13d10b75f203792384._comment diff --git a/doc/forum/XMPP_authentication_failure/comment_3_1a7ff955e9173f13d10b75f203792384._comment b/doc/forum/XMPP_authentication_failure/comment_3_1a7ff955e9173f13d10b75f203792384._comment new file mode 100644 index 0000000000..587daa0edc --- /dev/null +++ b/doc/forum/XMPP_authentication_failure/comment_3_1a7ff955e9173f13d10b75f203792384._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 3" + date="2013-04-12T22:25:12Z" + content=""" +John has gotten back to me with some analysis. The authentication failure is when SCRAM-SHA-1 is used. Ejabberd is rejecting the client's authentication request with a reason of \"bad-protocol\". It's not clear if ejabberd is broken or if gsasl is generating a bad SCRAM-SHA-1 authentication. We're inclined toward the latter, and will be forwarding this on to ejabberd. + +The only way to turn off this authentication in ejabberd is to configure it to store passwords in plain text, or downgrade to a version older than 2.1.9, which first added it. Note that debian stable contains 2.1.5.3, so is not currently affected, for example. +"""]]