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

Re: Could not obtain the list of SASL mechanisms

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Sun, 25 Jul 2010 17:55:28 +0200

On 24.07.2010 13:44, Ad wrote:
> Hi Stefan,
>
> With the reference of your post on:
> http://groups.google.com/group/tortoisesvn/browse_thread/thread/f3f7b4818db241a8
> thread, I have some query.
>
> I am stuck with the same problem. In my case, I have configured the
> svnserve.conf as per the standard style.
>
> svnserve.conf
> --------------------
> [general]
> anon-access = none
> auth-access = write
> # password-db = passwd
> # authz-db = authz
> realm = Temp Repository
>
> [sasl]
> use-sasl = true
> min-encryption = 128
> max-encryption = 256
>
> and, the svn.conf file is placed in my Windows 7 computer at 'C:
> \Program Files\CollabNet\Subversion Server' which (as you mentioned)
> is my SVN working directory. The registry key value is set

Move your working directory out of c:\program files.
It doesn't belong there, and Win7 has therefore put a lot of
restrictions on that directory and all subdirectories of it.

> accrodingly. Still, I am getting the "Could not obtain the list of
> SASL mechanisms" error in TSVN client. Can you help me in this
> problem?

Check the svn.conf file: in there you have to specify which sasl
mechanism you want to use. If you specified one that TSVN doesn't ship
with, it won't work.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2637977
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-07-25 17:55:41 CEST

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

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