Re: Limit Password Retry

[Quinn Taylor]

My guess is that implementing something like this would (a) be tricky, and (b) reduce performance. The reason I say that is because repository checking is most likely run concurrently, and defining groups that use the same account and password would require additional overhead, and require either Versions to infer which are actually the same account (could be used on different URLs) or the user to specify the groups.

 - Quinn

On Sep 23, 2009, at 8:19 AM, ChesterCopperpot wrote:

There is a simpler solution for the (probably) infrequent case of changed passwords: quit Versions, open Keychain Access, search for "svn", and change your password for that account for every server login that uses it. When you relaunch Versions, it will use the new password(s) from your Keychain. Also, I think most of us don't have SVN accounts that auto-lock after N incorrect password attempts, so this feature would probably be of limited (if any) utility to most users.

If I am connected to several repositories, and my password changes.
Versions will automatically attempt to reconnect all of my
repositories with my old password, locking my account. Possible
solutions.

- If one fails, prompt the user to verify, before connectin.
- have password groups, so you can assign a whole bunch of
repositiories to one group
- hook up the password to your user password on that computer.  So it
always tries that first unless otherwise speficied.

smime.p7s
Description: S/MIME cryptographic signature