Thanks for your quick answer !! Subversion runs under a Windows Server 2008 x64. I use subversion only to save my personal works. I think I reinstall the previous version or use basic authentification.
Thanks for all Olivier 2011/12/13 Stefan Sperling <s...@elego.de> > On Tue, Dec 13, 2011 at 06:07:19PM +0100, olizit wrote: > > Hi, > > > > I update my own svn server from 1.6.11 to 1.7.2. > > I use sasl encryption for authentification. > > saslpasswd2 works perfect on 1.6 version but seems not work in 1.7.2. > > Password database file (sasldb in my case) seems to be not created. > > Are you tested this kind of configuration ? > > Do you know if something changed in authentification process ? > > > > Thanks for all. > > > > Olivier > > There have been no significant changes in Subversion's SASL support > code between 1.6 and 1.7. However, we keep getting some reports about > problems with SASL after upgrading to 1.7. > > In all cases so far, the problem seemed to be in the cyrus-sasl package > rather than in Subversion. It is possible that a problem in cyrus-sasl > is coinciding with the upgrade to Subversion 1.7, making it look as > if Subversion 1.7 SASL support had a regression. But it is just as likely > that a recent cyrus-sasl upgrade introduced a problem. > > For instance, see this post, and the replies, from just a few days ago: > http://svn.haxx.se/users/archive-2011-12/0150.shtml > > On OpenBSD, a Subversion SASL problem was identified as a problem with > the SASL package: http://marc.info/?l=openbsd-ports&m=131805779110751&w=2 > I don't know if other systems, such as Linux, have had similar issues. > > You have not told us which operating system you are running. >