Re: SASL Interoperability

On Thu, 2003-05-29 at 09:10, Paul Andrews wrote:
> And finally ( :-) ):
>  
> I've been using the Java beepcore implementation against the C
> beepcore implementation (or more properly with the Cyrus SASL
> libraries) and come across a couple of interoperability issues.
>  
> The first was with the base64 encoding of <blob>s. The Java SASL
> libraries split the encoding across multiple lines - the Cyrus SASL
> libraries expect it all to be on one line. At first, I though that
> RFC3080 was vague on this issue, but it does say in its examples that
> although the text is split across multiple lines, in actuality, the
> blob wouldn't be. However, it is read we would increase
> interoperability if we *didn't* split across multiple lines.

I agree this should be fixed in beepcore-j. I'm currently refactoring
the tuning reset code so I won't be able to get to this for a few days.
If you need it sooner and would like to submit a patch I'm happy to
check it in.

> The second is really a problem with the Cyrus libraries, but I'll
> include it here in case anyone reading can influence the Cyrus group.
> RFC2831 (SASL/DIGESTMD5) states that 'qop-options' is optional and
> defaults to "auth" if not specified. Cyrus simply aborts the exchange
> if it isn't specified.

I don't know much about SASL but is there something that could be
changed in beepcore-j to make this work?

--Huston



-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5