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

Re: Bug in ra_serf with client certificates

From: Branko Čibej <brane_at_wandisco.com>
Date: Tue, 28 Jan 2014 14:46:30 +0100

On 28.01.2014 14:37, Lieven Govaerts wrote:
> On Tue, Jan 28, 2014 at 1:53 PM, Branko Čibej <brane_at_wandisco.com> wrote:
>> I just got a private report from a user that has a setup with a private
>> certificate. This user happened to select the wrong certificate for a
>> server, and got the following response:
>>
>> svn: E120171: Unable to connect to a repository at URL
>> 'https://example.com/svn/foobar'
>> svn: E120171: Error running context: An error occurred during SSL
>> communication
>>
>>
>> This the error code E120171 comes from Serf and apparently means
>> SERF_ERROR_AUTHN_FAILED. There's corroboration in the server log:
>>
> 120171 = SERF_ERROR_SSL_COMM_FAILED

Ugh. That's me looking at the wrong part of serf.h. :(

> The command line client doesn't ask for a client certificate, it
> should be defined correctly in the servers file using:
> ssl-client-cert-file
> ssl-client-cert-password

(facepalm)

> Unless (s)he's using TortoiseSVN which has its own dialog to select
> certificates from the windows certificate store.

It's not TSVN, it's a different client but the result is the same -- it
has its own implementation of the authn callback.

In other words, is I expect there's no way to get the authn dialog to
ask for a different cert, given the error message; thanks, I'll pass
this on.

-- Brane

-- 
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane_at_wandisco.com
Received on 2014-01-28 14:47:09 CET

This is an archived mail posted to the Subversion Dev mailing list.