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

Re: svnserve SASL documentation?

From: Malcolm Rowe <malcolm-svn-dev_at_farside.org.uk>
Date: 2007-04-10 23:10:14 CEST

On Tue, Apr 10, 2007 at 12:10:23PM -0700, Eric Gillespie wrote:
> The only answers i've heard so far were basically "sniff the
> traffic" and "poke around your system package database for sasl
> modules". This isn't acceptable.

So I was the crazy person suggesting those as possible approaches to
debugging why Eric's SASL-enabled binary just says 'hey, no mechs',
which might be fine for Eric, but isn't going to fly for users.

Part of the problem, of course, is that SASL is designed to be a black
box - we ask it to authenticate, and it returns 'okay' or 'no mechs' or
similar. That said, there must be ways to improve the user experience.

For example, could we get a list of the client mechs and return those to
the user when we get the 'no mechs' message? How about the server mechs?

I'm sure there's more that we could do.


  • application/pgp-signature attachment: stored
Received on Tue Apr 10 23:11:30 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.