> Thank you both very much for your quick replies. This definitely
> helps as it will allow us to at least function with CAC support for
> the latest version. However, I'm assuming that this still functions
> as it did in 1.5.5, with a prompt for each action (and multiple times
> when brining up the repository browser). Is there any way to make it
> default to a particular certificate?
No, that's the reason why I disabled it again in TSVN.
To get such a feature (e.g., using a default certificate or even save a
specific certificate like the "save authentication" does for 'normal'
authentication) it has to be implemented in the Subversion library and
btw: if you guys keep compiling TSVN yourself to get capieng compiled
in, but don't send mails to the Subversion list asking for this feature,
it will never get implemented. Seriously, send mails there and request
> Also, do you have any pointers for the Apache configuration? We
> thought we had it figured out but something is wrong. When we access
> the repository through a web browser, we are prompted for a CAC and
> can access the site. However, pointing TortoiseSVN to the same URL
> results in a prompt for a file based certificate, even with version
Did you specify
<arg value="-DOPENSSL_CAPIENG_DIALOG" />
in the OpenSSL.build file?
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 2009-05-04 19:37:35 CEST