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

Re: Only two Windows binary distribution support SASL encryption?

From: Mark Phippard <markphip_at_gmail.com>
Date: Fri, 5 Nov 2010 16:59:12 -0400

> I have the Win 2003 server set up with SASL and encryption, as
> stated earlier this week.
> The relevant portion of svnserve.conf:
>  [sasl]
> use-sasl = true
> min-encryption = 128
> max-encryption = 256
> and svn.conf:
> pwcheck_method: auxprop
> auxprop_plugin: sasldb
> mech_list: DIGEST-MD5
> sasldb_path: C:\Subversion\conf\sasldb
> I tried all the Windows binaries on the binaries download page.
> Only SlikSVN and WANdisco are able to talk to the repository. All
> other fail with "svn: Cannot negotiate authentication mechanism"

When I have tested the CollabNet binaries in the past they supported
this fine. The Cyrus SASL stuff requires registry entries to work
properly. If you are trying all of these from the same workstation
are you checking those entries?

I know I have Subclipse users that use SASL via installing those
binaries. I do not know which options they use.

In general, I think it was a mistake that we ever allowed the SASL
stuff into our code base. The required dependencies are poorly
documented which just makes SVN look bad and it does not accomplish
the main goal virtually every user wanted, which was to connect to
Active Directory.

IMO, Apache server is still the best way to go.

Mark Phippard
Received on 2010-11-05 21:59:52 CET

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

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