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

Re: Replacing --no-auth-cache with something better

From: Tobias Ringstrom <tobias_at_ringstrom.mine.nu>
Date: 2003-12-11 18:17:32 CET

Philip Martin wrote:
> "C. Michael Pilato" <cmpilato@collab.net> writes:
>>I suggested exactly this kind of thing a while ago. Basically, you're
>>options would be:
>> --no-auth-cache : don't store anything
>> --safe-auth-cache : store usernames, but no passwords or
>> other "private" data
>> (nothing) : store it all
>>With per-server configs in ~/.subversion, of course.
> I like that as well. It restores the original behaviour of
> store-password (from the time auth data was stored in the WC) where it
> only affected the password and not the username.

Great, thanks!

I assume that this change would not be suited for 1.0. For 1.0 I'd like
to suggest an alternative minimal impact solution.

The biggest problem is that the configuration directive store-passwords
does more than it's name suggests, i.e. it disables storing of *any*
credentials, not only passwords. In fact is equivalent to the command
line option --no-auth-cache, so I propose to change the name of
store-passwords to store-auth-cache. We can add a real store-passwords
config option post 1.0.

I'll go ahead and produce such a trivial patch tonight, but I won't
commit it until we have decided how to manage changes at this point and
this change has been deemed safe enough.

I will start by creating an issue for this.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 11 18:18:55 2003

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.