Re: username/password caching

Philip Martin <philip@codematters.co.uk> writes:

> What's the state of libsvn_auth, is it supposed to work?

Technically, it's "done". We're ready for David Waite's client-side
certs provider now. :-)

> Back in the old days I set store-password=no to avoid having my
> password cached. When I committed I was only asked to enter my
> password, the username was obtained from the cached value in the
> working copy.
>
> That hasn't worked for some time. When I commit I have to enter both
> my username and my password, even though my username is present in a
> file in the working copy. Is this change deliberate?

Yes, it's my fault, I apologize. I noticed that we had a
--no-auth-cache commandline switch, and also had a 'store-password'
config file variable. I said to myself, "bah, these two things should
just map to the same concept. The only difference is that one is
temporary, and one is permanent."

I guess I was too eager to oversimplify. I didn't realize anyone out
there actually wanted something in between "cache nothing" and "cache
everything".

But cmpilato has already proposed a solution to get the halfway-state
back again. :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Feb 22 16:47:23 2003