[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: Malcolm Rowe <malcolm-svn-dev_at_farside.org.uk>
Date: 2007-01-04 23:18:08 CET

On Thu, Jan 04, 2007 at 11:56:16AM -0800, Daniel Rall wrote:
> 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?

Whoa, wait a sec. The whole point of SASL is pluggable auth - I
wouldn't want us to be making a policy decision (to fall back on
svn-native auth) based on the presence or absence of particularly-named
SASL auth modules. (Unless those are the only two we can use? But I
didn't think that was the case).

I'd prefer that we attempted SASL auth and failed back to native auth
only if that fails to find a matching mech. (I'm not sure, but it's
likely that that would require us to drop the connection and reconnect,


  • application/pgp-signature attachment: stored
Received on Thu Jan 4 23:18:25 2007

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