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

Re: Building Tortoise SVN 64 Bit

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Mon, 29 Mar 2010 19:44:26 +0200

On 29.03.2010 13:21, Markus Oberlassnig wrote:

>> I'm not sure, if you have understood me correct.
>> It does not matter how many certificate the user has in his CA store.
>> It only pops up, if the user has more than one private certificate
>> matching to the CA certificate of the server in his private
>> certificate store.
>> So, what are the requirement, that it pops up:
>> 1) Server requests a client certificate (for CA xy)
>> 2) There is more than one matching certificate in my private keystore
>> (matching means: the private key is issued by the CA xy)
> ***Correction of my previous entry***
> So, what happens if i don't have such a private certificate in my
> keysore.
> Then it pops up for the certificate file.
> If CAPI is not enabled it pops up for the certificate file and there
> is no possibility to read the certificate from the smartcard (if my
> organisation has planned to put the certificate on a smart card and it
> is not allowed to export from there).

I know that it doesn't work if you use smartcards. But that's always
been that way and won't break the compatibility. However, having a
dialog suddenly pop up every time a repo is accessed is a major

I'm not sure though why someone would have two or more private
certificates matching the CA certificate on the server. Would that be a
buggy configuration? Or is it sometimes necessary to have more than one?


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-03-29 19:44:33 CEST

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

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