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

Replacing --no-auth-cache with something better

From: Tobias Ringström <tobias_at_ringstrom.mine.nu>
Date: 2003-12-11 00:01:08 CET

I'd like to straighten out a small but confusing issue with the auth
system, but I'd like to hear your opinion before I go ahead.

The auth system today has an option to prevent saving of *any* kind of
credentials. Since there is only one global option, it is not possible
to prevent storing of e.g. passwords without also making it impossible
to e.g. trust SSL server certificates permanently.

I'd like to replace this global setting with a setting for each
authentication provider that needs it, i.e. the simple password and
username authentication providers. Making such a change will also make
it possible for the front-end to decide if e.g. a password should be
saved or not. In other words, it will be possible to implement a
username and password dialog box with a "remember password" checkbox.

That also means that the command-line option --no-auth-cache needs to be
renamed to --no-password-store or something similar. Suggestions for a
better name are most welcome.

Another option is to *not* remember passwords by default and to
implement a --remember-passwords option instead. It sounds better, it
is a little safer, but it's also a little bit more annoying.

Please let me know what you think!


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 11 00:01:48 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.