Re: [PATCH] Change default "store-passwords" policy to "no"

On 10/11/07, Ben Collins-Sussman <sussman@red-bean.com> wrote:
> My preference is that after successful authentication, the default
> behavior is to *ask* the user whether to cache the password on disk.
> (And the prompt should make it clear whether the cache will be
> encrypted or not.) This is what web browsers do, and that's a UI
> that everyone is familiar and comfortable with.
>
> (It sort of matches the way we prompt about accepting new SSL
> certificates: never, for this session only, or permanently.)

AFAIK, Subversion already has this functionality. I think the CLI
just does not use it. When a user is using Subclipse, as an example,
we receive a callback from JavaHL that asks for username/password AND
whether the user wants to cache the password. The problem (I think)
is if you set store-passwords=no, then the user will no longer get
that option to store the password. I think that would be an
unacceptable regression.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org