On 9/26/06, David Glasser <glasser@mit.edu> wrote:
> On 9/25/06, Vlad Georgescu <vgeorgescu@gmail.com> wrote:
> > With this patch, you can run 'make svncheck ENABLE_SASL=true' or 'make
> > svnserveautocheck ENABLE_SASL=true' and all authentication requests
> > will be handled by Cyrus SASL.
>
> Vlad:
>
> This looks good. I'm wondering though: I'm not too familiar with
> SASL, but is it easy to set up non-global SASL configurations? Having
> to run stuff as root and/or introduce fake users into a system
> database during tests seems non-ideal. Could we possibly make
> ENABLE_SASL=true automatically make a SASL configuration for you?
> (I'm happy to do the legwork if you can point me at the appropriate
> SASL commands and/or flags.)
Note that you don't have to be root, on my system I just had to add
myself to the sasl group before I could run saslpasswd2. It doesn't
seem easy to set up a non-default sasl db though, although I agree
that would be nice.
I will say though that this isn't any more complex than our setup for
testing over ssh, or for DAV on a system where you don't have a
functional davautocheck.sh. Adding two arbitrary users to the sasl db
doesn't seem like that big a deal. They're using a realm that's
unlikely to conflict with normal use (svntest), and you only have to
do it once and then those users are there for any subsequent test you
want to run.
-garrett
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 26 21:50:20 2006