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

Strange authentication errors

From: Matt Larson <mlarson_at_verisign.com>
Date: Wed, 18 Jun 2008 11:16:23 -0400

Folks,

I just migrated some svn repos from one server to another. The old
server was Apache 2.0.54 and Subversion 1.2.3. The new server is
Apache 2.2.3 and Subversion 1.4.6. All repos use simple digest
authentication (i.e., mod_authz_svn.so) using files. Most repos are
available over both HTTP and HTTPS.

I'm writing because I'm having weird authentication failures. Access
from a web browser to all the repos over both HTTP and HTTPS works
fine. Access from svn command-line clients is hit and miss and that's
my problem.

From a Mac (MacOS 10.4.11) with svn 1.2.3, an "svn ls" (and other
operations) work fine over HTTPS. Over HTTP, I get this:

  zephyr:/tmp$ svn ls http://svn.verisignlabs.com/unbound
  Authentication realm: <http://svn.verisignlabs.com:80> unbound.rfc.se
  Password for 'matt':
  [Multiple password entry attempts deleted]
  svn: PROPFIND request failed on '/unbound'
  svn: PROPFIND of '/unbound': authorization failed (http://svn.verisignlabs.com)

I assure you that the password is configured correctly and I'm typing
it correctly, since this same password works over HTTPS. (I've also
reset it at least once to assure the digest file entry is correct.)

From a Linux box (Fedora Core 7) with svn 1.4.4, I get authentication
failures over both HTTP and HTTPS. The HTTP failure looks identical
to above. The HTTPS failure is different:

  monsoon:~$ svn ls https://svn.verisignlabs.com/unbound
  Authentication realm: <https://svn.verisignlabs.com:443> unbound.rfc.se
  Password for 'matt':
  svn: PROPFIND request failed on '/unbound'
  svn: PROPFIND of '/unbound': SSL negotiation failed: Connection reset by peer (https://svn.verisignlabs.com)

Both the Mac and the PC are on the same LAN segment (same switch,
even), so that should eliminate network problems.

Meanwhile, a colleague reports success access this same repo over both
HTTP and HTTPS from another network using a Fedora 9 box with svn 1.4.6
and another Linux box using an svn 1.3.2 client.

The hit and miss nature of this problem has me pounding my head. I'd
appreciate any suggestions, pointers, advice--anything.

Thanks for your help,

Matt Larson
<mlarson_at_verisign.com>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-18 17:17:07 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.