Malcolm Rowe wrote:
> On Tue, Apr 10, 2007 at 02:15:03PM -0700, Eric Gillespie wrote:
>>> 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?
>> What would the user do with that information?
>>
>
> Work out whether they've configured SASL correctly? We're relying on a
> shared resource - the SASL configuration - and asking the SASL libraries
> to 'do authn' for us (that being, after all, the whole point of SASL).
> Someone setting up a SASL-enabled server _needs_ to understand how to
> configure SASL in the first place, and I'm just suggesting that we could
> go some way to help them understand what's happening.
>
> For example, if you got something like the following:
>
> svn: auth error: no worthy mechs [or whatever it says now, followed by:]
> Client authentication mechanisms: { ANONYMOUS, CRAM-MD5 }
> Server authentication mechanisms: { KERB-MIT }
[...]
Yes, that's doable. SASL provides an API for fetching the local list of
mechanisms. I'll look into it.
--
Vlad
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 11 00:12:57 2007