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

Re: Support for CryptoAPI

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Thu, 02 Oct 2008 13:21:32 +0200

Marcus Kovács wrote:
> Wow, that was fast. Unfortunately my tests didn't pass through using
> TortoiseSVN nightly build. I checked the OpenSSL.build file and it
> looks fine but there is not a trace of the "enable-capieng" in the
> buildlog. Perhaps this is not an issue.

the script runs
$ perl Configure VC-WIN32 enable-capieng
-DOPENSSL_SSL_CLIENT_ENGINE_AUTO=capi
(on one line)

as you suggested.

from the buildlog
(http://nightlybuilds.tortoisesvn.net/latest/win32/buildlog.txt) I can
also see that e_capi.c is linked in.
And OPENSSL_NO_CAPIENG is *not* defined, so it should work.

I think you know more than I do about building OpenSSL and the configure
script :)

> The testcase failed by fronting me with a File selection dialog to
> choose certificate instead of having OpenSSL pick one from the
> certificate store or listing available certificates in the store.
> Seems like the certificate request is not handled by the OpenSSL
> library but interferred by this dialog at some point. Do you have any
> ideas why this could be ?

That dialog is shown when the server requests a certificate file, and
that request is passed on to the svn library (which then passes it on to
TSVN, which shows the file-open dialog).
If capieng would handle such requests before passing them on, you
shouldn't see that dialog at all.

Can you try building TSVN yourself? Do you maybe have a public test
server where I can connect my build of TSVN to?

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net

Received on 2008-10-02 13:21:52 CEST

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