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

Re: Totoise SVN and non-public certificate

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Thu, 17 Nov 2011 12:59:33 +0100

On Thu, Nov 17, 2011 at 09:07, Frank Breedijk
<fbreedijk_at_schubergphilis.com> wrote:
> Hello,
> We run an SVN repository protected with a certificate issued by our own internal CA. This CA is added to the windows certificate store and thus these certificates validate nicely when we brows to our svn repository.
> However when Tortoise connects to the repository I get this error message:
> Unable to connect to a repository at URL 'https://svn.xxx.lan/xxx/trunk'
> OPTIONS of 'https://svn.xxx.lan/xxx/trunk': Could not read status line:
>  SSL error: sslv3 alert certificate unknown (https://svn.xxx.lan)
> It appears that Tortoise does not use the windows cert store, but an internal certificate store, how do I add the CA certificate to the store or make Tortoise prompt me to accept the certificate?

you also have to add the internal CA to the cert store. Otherwise the
cert in your store can not be validated: the error does not tell you
that there is no certificate, but that the certificate (which is
there, so Subversion found it) is unknown, i.e. not verified.


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-11-17 13:00:04 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.