"Sean McBride" <sean_at_rogue-research.com> writes:
> On some computers only, 'svn info' is always giving:
> svn: E120171: Error running context: An error occurred during SSL communication
> when connecting to our own svn server. This worked previously, but
> stopped working (I think) after our self-signed certificate expired
> and was therefore replaced. First we replaced it with another
> self-signed cert, then we replaced it with a purchased wildcard cert.
> - I reproduce this with svn 1.8.10 (Wandisco binaries on OS X) on the client.
> - Server runs 1.7.18 (Wandisco binaries on OS X).
> - I have deleted ~/.subversion on the client, no help.
> - I created an entire new user account on the client machine, no help.
> - visiting https://my.server.com/path/to/repository in a browser (tried several) prompts for authentication, succeeds, and shows the expected files.
> - I ran "openssl s_client -showcerts -connect <my.server.com>:443" and it reports at the end:
> "Verify return code: 0 (ok)"
> I'm now feeling pretty stuck. :( Any suggestions on what this problem
> is, or how I can diagnose it further?
Is apache using SSLVerifyClient to require the client to provide a
certificate? The 1.8 client defaults to not prompting for a client cert
if no cert is configured and that will cause the error you report. See:
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Received on 2014-10-24 17:26:18 CEST