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

Re: svncpp crash in ssl_server_trust_file_save_credentials

From: Tobias Ringstrom <tobias_at_ringstrom.mine.nu>
Date: 2004-01-21 14:42:01 CET

Barry Scott wrote:
>> No, that is not how it works. If the may_save argument to the prompt
>> function is FALSE, it means that it is impossible to save. Even if you
>> set may_save in the creds struct to TRUE, it will not be saved. If the
>> application wants to remember a default setting for the user, it must
>> do so in an application specific way (probably utilizing the prompt
>> baton). That has nothing to do with the svn libs.
> Let me check I understand.
> The may_save means that there is no provider capable of saving the
> credentials.
> However in the case of the svncpp library I will always see may_save as
> true as it adds the file providers. Hence I could remove the may_save flag
> for the API and simplify the C++ and pysvn API.
> I'm guessing you are going to say I have this wrong :-)

I'm afraid I have to. It is possible to globally disable saving of
authentication credentials by setting store-auth-creds to "no" in the
config file. The command line client also has an option --no-auth-cache
which does the same thing. The may_save that is passed to the prompt
function is set to FALSE if any of these options are used.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 21 14:42:36 2004

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

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