Re: svn always fails with E120171, but only from some clients

2014-10-24 Thread Philip Martin
"Sean McBride" writes: > On Fri, 24 Oct 2014 16:24:58 +0100, Philip Martin said: > >>Is apache using SSLVerifyClient to require the client to provide a >>certificate? > > I'm not too familiar with apache, but I'm going to say "no", which I > conclude from this: > > $ cd /Library/Server/Web/ > $ g

Re: svn always fails with E120171, but only from some clients

2014-10-24 Thread Sean McBride
On Fri, 24 Oct 2014 16:24:58 +0100, Philip Martin said: >Is apache using SSLVerifyClient to require the client to provide a >certificate? I'm not too familiar with apache, but I'm going to say "no", which I conclude from this: $ cd /Library/Server/Web/ $ grep -R -i SSLVerifyClient * which find

Re: svn always fails with E120171, but only from some clients

2014-10-24 Thread Philip Martin
"Sean McBride" 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 certificat

Re: svn always fails with E120171, but only from some clients

2014-10-24 Thread Lieven Govaerts
On Fri, Oct 24, 2014 at 4:49 PM, Sean McBride wrote: > Hi there, > > 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 > workin

svn always fails with E120171, but only from some clients

2014-10-24 Thread Sean McBride
Hi there, 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 therefor