problems with clients and cyrus-sasl-2.1.22
Alexey Melnikov
alexey.melnikov at isode.com
Thu May 25 10:32:07 EDT 2006
Andreas Hasenack wrote:
>On Thu, May 25, 2006 at 02:43:17PM +0100, Alexey Melnikov wrote:
>
>
>>>bm9uY2U9IkVZMEI5anR4NlNsc0tQSGhHTGovNmI4WW1qQ3BadDZCL1RGUXAva21kUEU9IixyZWFsbT0icGFuZG9yYS5jb25lY3RpdmEiLHFvcD0iYXV0aCxhdXRoLWludCxhdXRoLWNvbmYiLGNpcGhlcj0icmM0LTQwLHJjNC01NixyYzQsZGVzLDNkZXMiLG1heGJ1Zj00MDk2LGNoYXJzZXQ9dXRmLTgsYWxnb3JpdGhtPW1kNS1zZXNz
>>>base64 decoding error
>>>
>>>
>>Ah, I've fixed base64 decode function ;-). This might have broken imtest.
>>
>>
>Is the fix correct and imtest was relying on a bug?
>
>
I think the issues is that imtest passes base64 string terminated with
CRLF to sasl_decode64.
This "feature" was removed from sasl_decode64, as CR and LF are not
valid base-64 characters.
More information about the Cyrus-sasl
mailing list