On 05.06.2013 09:25, Markus Schaber wrote:
Hi, Stefan,
Von: Stefan Küng [mailto:tortoise...@gmail.com]
On 04.06.2013 13:56, Lieven Govaerts wrote:
You are referring to a configuration where OpenSSL uses MS's CryptoAPI
to use the Windows certificate store. Never used it myself, but I see
that TSVN has implemented this, with an extra dialog to select a
client certificate if multiple were found.
I see no reason why that won't work with serf, we probably would have
heard about it if not.
So for Windows there's no problem, only for Mac & Linux we don't have
a smart card solution in 1.8.0 at this time.
Some information about this:
[...]
This patched version of the CAPI engine in OpenSSL is already in use in a
company and works fine there.
In case you're interested: the patch for e_capi.c in OpenSSL is here:
https://tortoisesvn.googlecode.com/svn/trunk/ext/build/openssl.patch
Just out of curiosity: Did you try to upstream your changes for inclusion in
OpenSSL?
no, I didn't: I doubt it would have the slightest chance to get included
since it's basically an ugly hack to get what I need. A real solution
would require not only changing the OpenSSL code but then also serf and
even svn to use those changes in OpenSSL.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net
