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

<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 wcA
>
> store-password = yes
> svn co https://foo.com/trunk foobar --auth-cache
> -----------------------------------
> username is stored in wc
> password is stored in wcA
>
> 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.

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

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org