On 18.02.2016 10:00, Stahn Roland wrote:
> Hi,
>
> I use both Commit Monitor 1.11.1.1099 (64bit) and TortoiseSVN 1.9.2
> (64bit) to access a SVN repository with client certificate
> authentication. This used to work fine.
>
> After an OS upgrade on the server side (no settings changed) I face a
> strange problem regarding the client certificate authentication.
>
> TortoiseSVN can access the repository without any problem, but Commit
> Monitor reports “An error occurs during SSL communication”.
>
> I have tracked down the symptoms to the following point:
>
> Commit Monitor fails to access the server, if the client certificate is
> present in the Windows certificate storage.
>
> If I remove it from the Windows storage and configure it in the
> “servers” file only, then Commit Monitor is suddenly able to access the
> repository.
>
> TortoiseSVN (and its Project Monitor) is able to connect to the server
> in either configuration.
>
> Are there any important configuration differences between Commit Monitor
> and TortoiseSVN that I am not aware of?
>
One difference is that TSVN can handle situations where multiple
matching certificates are in the local store: it then shows a dialog
where you can select the correct certificate, and it then saves that
certificate and doesn't ask anymore for it.
CM always uses the first certificate that matches the server request -
whether that certificate is still valid or not. It never shows a cert
selection dialog.
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=3161473
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2016-02-18 19:02:59 CET