Re: username/password caching
From: <cmpilato_at_collab.net>
Date: 2003-02-22 04:30:09 CET
Philip Martin <philip@codematters.co.uk> writes:
> Hello
For a period of time during the auth system transition, none of the
--- Ben: remember how you and I were thinking it was ridiculous that the config option "store-password" was only about storing the password, yet the --no-auth-cache command-line option was for not storing *any* creds, and we talked about making them do the same thing (either store all or store none)? I've been thinking about that some more. On the one hand, giving the user only the options of "store everything" or "store nothing" means they might have to provide both a username and password for each committing command. That could get annoying. Then I thought, what if each provider's "save" function accepted a flag that dictated the amount of data to save: 'none' - store no creds (but the system would call the function anyway in case the provider needs to do some kind of cleanup or admin task). 'username' - store a username only. 'all' - store all the creds. Then, we would change the config option to "auth-cache-type" (and the valid values would be 'none', 'username', or 'all', defaulting to 'username') and then change the command-line argument to "--auth-cache-type" with the same three valid values. This would let the super-paranoid choose to be annoyed by requests for usernames (where getuid() didn't pan out, of course), would let the average joe at least cache the username, and then would allow the carefree to enable full caching (also called "stop pestering me mode"). Thotz? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org For additional commands, e-mail: dev-help@subversion.tigris.orgReceived on Sat Feb 22 06:32:08 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.