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

Re: Compiling with capieng enabled for smart card authentication

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Tue, 14 Apr 2009 18:30:54 +0200

Lucas Johnson wrote:
> I read a post by someone else who mentioned that version 1.5.5 of TortoiseSVN had the capieng enabled by default. This option has to be turned on before smart cards, or Common Access Cards (CAC), can be used for authentication. I tried version 1.5.5 and it worked perfectly for me. However, when I try to custom build version 1.6.0 or 1.6.1, these are the only two versions that I have tried so far, I cannot get smart card authentication to work with the options that I believe are turned on in version 1.5.5. I have followed the instructions in the build.txt file and I can successfully build the resulting Windows installer package (.msi) file. So I have modified default.build.user, doc/doc.build.user, Languages.txt, and OpenSSL.build. In OpenSSL.build my win32 section looks like the following:
>
> <if test="${platform == 'win32'}">
> <exec program="perl" workingdir="..\..\..\common\openssl">
> <arg value="Configure" />
> <arg value="VC-WIN32" />
> <!-- added the following three args to enable CAC authentication -->
> <arg value="enable-capieng" />
> <arg value="-DOPENSSL_SSL_CLIENT_ENGINE_AUTO=capi" />
> <arg value="-DOPENSSL_CAPIENG_DIALOG" />

If you don't want the dialogs, remove the last line.

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1712841
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].

Received on 2009-04-14 18:31:16 CEST

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.