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

Re: [PATCH] default to --no-auth-cache

From: <rbb_at_rkbloom.net>
Date: 2003-01-13 23:17:40 CET

On 13 Jan 2003, Philip Martin wrote:

> <rbb@rkbloom.net> writes:
>
> > So, the Use Cases:
> >
> > store-password = yes
> > svn co https://foo.com/trunk foobar
> > -----------------------------------
> > username is stored in wc
> > password is stored in wc
> >
> > store-password = yes
> > svn co https://foo.com/trunk foobar --auth-cache
> > -----------------------------------
> > username is stored in wc
> > password is stored in wc
> >
> > store-password = no (This ends up being the default mode)
> > svn co https://foo.com/trunk foobar
> > -----------------------------------
> > username is stored in wc
> > password is not stored in wcA
> >
> > store-password = no
> > svn co https://foo.com/trunk foobar --auth-cache
> > -----------------------------------
> > username is stored in wc
> > password is stored in wc
> >
> > Does that make sense now?
>
> Frankly, no. There is no way to avoid storing the username. Also, I
> don't see why you want to change -no-auth-cache to --auth-cache if the
> third case is the default.

I am having a hard time figuring out why you would want an option to not
store the username. Perhaps if you could explain why that is desireable,
I would understand the goals of --no-auth-cache and store-password better.

> If the use cases above are really what you want then I think you
> should change the store-password default and leave --no-auth-cache as
> it is
>
> Case 1: the default, store-password = no, doesn't have --no-auth-cache
> username is stored
> password is not stored
>
> Case 2: store-password = yes, doesn't have --no-auth-cache
> username is stored
> password is stored
>
> Case 3: --no-auth-cache, store-password is irrelevant
> username is not stored
> password is not stored

The problem with this, is that it becomes impossible to get your password
into the cache if you decide you want it there, without modifying your
~/.subversion config file. That may be okay if you can set store-password
on a per-project basis, but I don't see a way to do that.

Ryan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 13 23:04:32 2003

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