[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SASL auth failure, reported by Cyrus SASL as "no mechanism available"

From: Vlad Georgescu <vgeorgescu_at_gmail.com>
Date: 2007-01-04 22:34:16 CET

On 1/4/07, Daniel Rall <dlr@collab.net> wrote:
> On Thu, 04 Jan 2007, Vlad Georgescu wrote:
> > On 1/4/07, Daniel Rall <dlr@collab.net> wrote:
> > >I'm of a similar mind to Malcolm here -- why don't we do something
> > >more user-friendly here? Would falling back to simple_auth.c do the
> > >trick?
> >
> > Yes it would. SASL doesn't make it particularly easy to do this kind
> > of stuff, but I'll look into it.
> Thanks Vlad. How does SASL load its plug-ins? sasl/saslplug.h's
> sasl_server_plugin_info() API looks potentially useful here:
> /* Dump information about available server plugins (separate functions should be
> used for canon and auxprop plugins */
> LIBSASL_API int sasl_server_plugin_info (char *mech_list,
> sasl_server_info_callback_t *info_cb,
> void *info_cb_rock);

Nice! Just what I was looking for.

> If we compiled both sasl_auth.c and simple_auth.c, could we
> interrogate the installed Cyrus SASL plug-ins at Subversion library
> initialization time, and fall back to simple_auth.c if both the
> ANONYMOUS and CRAM-MD5 plug-ins aren't available?

Yeah, I think it should work. Thanks!

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 4 22:34:25 2007

This is an archived mail posted to the Subversion Dev mailing list.