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

Can't authenticate with svnserve + SASL

From: Rippit the Ogg Frog <rippit_at_oggfrog.com>
Date: Mon, 10 Aug 2009 10:18:53 -0700 (PDT)

Greetings, I just registered at Tigris.org.

I have set up an svnserve server with Cyrus-SASL digest-md5 authentication, but when I try to do an "svn co" I always get:

svn: Authentication error from server: SASL(-13): authentication failure: client response doesn't match what we generated

That sounds like it thinks I'm entering an incorrect password, but I'm quite certain I've got it right. Just to make sure, I've reset my password on the server several times, including setting a very simple, easy-to-type password.

Before I set up this server, I set up svnserve+SASL on a local Linux box just to make sure I understood how it all would work, and I was able to authenticate just fine.

However, that was using Fedora 11, whereas my production server runs Slackware 8, and required that I build Subversion, Cyrus-SASL, the Apache Portable Runtime and APR-Utils from source.

I got the Subversion and Cyrus-SASL sources from Slackware 12 and backported the SlackBuild scripts to build Slack packages on Slackware 8. I created Slack packages for APR and APR-Utils manually.

If there is a problem with the versions of things I could build my Slack packages with the latest sources.

Here are all the versions. First my client:

Mac OS X 10.5.7 Intel
Subversion 1.5.4 (from Apple Xcode 3.1.2)

Server:

Slackware 8
Subversion 1.5.4
Cyrus-SASL 2.1.22
Apache Portable Runtime 1.3.8
APR-Util 1.3.9

Thanks for your help! -- Rippit

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2382136

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-10 20:14:56 CEST

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.