Smack sends single equals sign ('=') as SASL response

Description

I have a little issue with this portion of code from SASLMechanism.java concerning the element

This codes send a '=' instead of an empty response element. '=' is not a valid base64 string. This is generally the last response of a challenge so many servers don't check the additional data but some like jabberd2 check it and send an incorrect-encoding failure. I attach the corresponding exchange.

Environment

None

Attachments

1

Activity

Show:

Robin Collier 
July 31, 2011 at 12:22 AM

Unfortunately, the fix was applied to trunk instead of the 3.2 branch so it did not get included in the 3.2.1 release. Luckily it is a simple fix, so it will be easy to apply to 3.2.2.

Walter Ebeling 
July 7, 2011 at 9:44 PM

Unfortunately there are report about this as being not fixed in 2.6.3.

http://community.igniterealtime.org/message/214456#214456

I am not sure how to deal with that.

Walter Ebeling 
March 27, 2011 at 7:17 AM

Looks like a patch that we want to include for RC2

Matt Johnston 
January 20, 2011 at 2:48 PM

This issue seems to affect most Android xmpp clients connecting to jabberd2. BEEM have patched it http://www.beem-project.com/projects/beem/repository/revisions/786 , I can confirm it works (no built package available yet).

Fixed

Details

Assignee

Reporter

Ignite Forum URL

Fix versions

Priority

Created July 27, 2010 at 4:43 PM
Updated October 28, 2020 at 1:28 PM
Resolved August 18, 2011 at 3:29 AM