On 22.03.2016 18:06, Chris Capon wrote:
> On 21.03.2016 , Stefan King wrote: > > On 21.03.2016 21:25, Ch ris Cap
> on wrote:
>> > TortoiseSVN v188.8.131.52038 > > When performing an Update using a
> connection which requires Client > > certificates, this versio n of To
> rtoiseSVN will save:> > > > - the location of t he clie nt certificate
> file > > - the login credent ials fo r the subversion server> > > > but
> will not save: > > > > - the password for the cli ent certificate file >
> > > > Attached is a photo of th e dialo g. I have tried clicking and
> unclicking > > the Save authentication c heckbox but haven't found a
> combination which > > preserves the password. This di alog appears every
> time. > > try the command line client. I f it do esn't save the password
> either, you > have to report it on the svn u sers li st. > I checked the
> code, and TSVN p asses t he 'save' flag properly to the svn > lib. So it
> should get saved... >
> Stefan What are the equivalent SVN command line
> options for the 'save' flag you are setting? When I run the command line
> client it always prompts for a certificate password. Thanks, Chris.
The default for the svn command line client is to always store the auth.
Unless you either pass "--no-auth-cache" on the command line, or you
have disabled auth caching in the subversion config file
Please check that file: if you have the line
# store-passwords = no
# store-auth-creds = no
set there without the '#' in front, then auth caching is disabled.
if you have neither of this, then you should report this on the svn
users list: then it's clear that the svn lib does not store this kind of
auth, even though it should.
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 2016-03-22 22:14:27 CET