On 6 Oct 2008, at 19:22, Mark Doliner wrote:
Cyrus SASL backend is currently abandoned and not maintained
anymore.
It has known bugs with noone wanting to fix them.
The main reason for Cyrus backend inclusion in jabberd2 was GSSAPI
support. GnuSASL backend has GSSAPI support now, too.
If the GnuSASL backend's GSSAPI support works correctly, then agreed
- the GSSAPI issue no longer remains. I have yet to evaluate the
support - last time I looked GnuSASL itself had somewhat suboptimal
support for GSSAPI (requiring calling applications to embed lots of
GSSAPI related logic themselves)
But the client support issues in GnuSASL with Digest-MD5 are a
significant issue for us. We simply can't mandate that our user
community use certain 'supported' clients. We haven't evaluated our
Jabber installation in a while. I suspect that the next time we come
to do so, faced with the choice between moving from Jabberd2 with
Cyrus to a Jabberd2 with a poorly-functioning GnuSASL, we'll end up
looking elsewhere.
I completely understand the arguments about standards compliance -
but we can't make those arguments to our users.
S.
--
To unsubscribe send a mail to [EMAIL PROTECTED]
