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

Re: ssl certificate path cacheing

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Tue, 11 Aug 2009 10:13:36 +0200

On 11.08.2009 02:05, David M. Chinn wrote:
> hello;
> I'm running 1.6.4 tortoise on windows against an apache server on linux.
> The windows client is running x64.
> Can't seem to get credentials cacheing right.
> I have ssl setup, so I access the repo with https. The server itself
> also has
> passwords set up.
> Everything works, except that the client doesn't seem to want to cached the
> path of the certificate... I go to the repo, and it asks for the cert
> path every time,
> even though I've checked the box that says 'Save client certificate path'
> The funny thing is that it knows the folder to open, it just won't
> remember the certificate
> to be used (the only file in the folder).
> I've gone to the 'saved data' screen on the tortoise settings context
> menu, and cleared
> the authentication data. When I do that, it asks for the cert password,
> and then gives
> me the server cert validation warning, and a finger print.
> It then asks for the apache password and user.
> At each stage, I ask it to save the data.
> But then, when I go back to the repo, pops open the folder dialog and
> asks me to select the
> client cert to use again.
> I've also tried uninstalling, and reinstalling, with the same effect.
> Any help would be appreciated.

Fixed in r16887.
You can however 'save' the path to the file by setting it in the
'servers' configuration file (settings->network->edit)


   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-08-11 10:13:48 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.