On 9/28/06, Vlad Georgescu <vgeorgescu@gmail.com> wrote:
> All our restrictions would still be enforced (this means no ANONYMOUS
> if auth-access is none etc.). Besides, this situation (SASL sending
> all mechanisms) also happens if there is no mech_list option in
> subversion.conf, which is perfectly OK. And there is no way we can
> reliably detect the absence of subversion.conf, so we don't really
> have a choice.
>
> The fix I was proposing (falling back to other mechanisms if GSSAPI
> fails) seems like a reasonable way to deal with these cases. The
> jabber guys seem to agree with me:
>
> http://j2.openaether.org/mediawiki/index.php/CyrusSASL#Client_considerations
Ok, works for me.
> > > OTOH, I'm not able to reproduce the problem Garrett described (the
> > > svnsync failures, or the valgrind errors). Everything seems to work
> > > fine. I'm using Cyrus SASL 2.1.22 on a FC5 box.
> >
> > FWIW, David appears to be able to make this problem happen on Mac OS
> > X, so it's not just me ;-)
> >
> > Could you try compiling your APR with --enable-pool-debug, and then
> > run svnserve under valgrind for the tests and see if you get any weird
> > errors? I use something like:
> >
> > valgrind subversion/svnserve/svnserve -d --foreground -r
> > `pwd`/subversion/tests/cmdline
> >
>
> OK, I'll try again with pool debugging enabled. Although it's weird
> that I didn't get any test failures, either.
Not all that weird. If it's a memory corruption problem it's bound to
be intermitent.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 28 21:38:38 2006