[asterisk-bugs] [Asterisk 0011644]: [patch] res_jabber appears to not be working correctly in /trunk

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11644 
====================================================================== 
Reported By:                davevg
Assigned To:                phsultan
====================================================================== 
Project:                    Asterisk
Issue ID:                   11644
Category:                   Resources/res_jabber
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 94978 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-27-2007 15:43 CST
Last Modified:              01-03-2008 07:36 CST
====================================================================== 
Summary:                    [patch] res_jabber appears to not be working
correctly in /trunk
Description: 
I did an in-place upgrade from a recent asterisk/branch/1.4 to
asterisk/trunk.  res_jabber did work correctly with 1.4 svn.  With the
trunk version every 4 seconds I receive this error:
[Dec 27 16:25:02] WARNING[16509]: res_jabber.c:1943 aji_recv_loop: JABBER:
socket read error
Both asterisk and jabber are located on the same server (CentOS 5) in this
instance.  See Additional info for details.
====================================================================== 

---------------------------------------------------------------------- 
 phsultan - 01-03-08 07:36  
---------------------------------------------------------------------- 
Thanks for the detailed report elguero, it looks like ejabberd does like
the password string we send, neither jabberd2 (I tested it too).

We compute a base64 value from the following string :
\0username\0password\0 , and jabberd2 refuses to authenticate by replying
with a <malformed-request> error. If we encode \0username\0password,
jabberd2 authenticates correctly. Please try the attached patch to see if
this works ok with ejabberd.

Openfire and Google's XMPP server seem less restrictive. Dave can you
confirm this new patch does break your authentication to you Openfire
server? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-03-08 07:36  phsultan       Note Added: 0076246                          
======================================================================