Re: How to force subversion to ask for username at a commit

> Are these users logging into the same account on all machines? I
> thought the cached credentials were on a per-host user account basis.
It really seems like the chaed credentials are on a per user bases. If you switch of password storing after you have one credential in the cache the cache will be overwritten just with a username without password on the next time you enter the user name when you update or commit...

The users are logged in with the same account. It is the account the whole simulation is running at. I know that sharing a WC is not a good thing, but in that case they share do not really share it. They use it for the moment until they commit their changes. Because for testing the whole simulation you need all machines in the lab with the same repo version checked out it is not really feasible to use a private user account on this machine.

What I did for the moment is that I removed password storing and all users use the same working copy for testing the simulation but everyone has to use his personal account during commits. Maybe I write a wrapper script around svn to add the mentioned read only credentials automatically when a user does an svn update so that you do not need to supply a password or user name on an svn update.
But in the end it comes down to storing the password in plain text in a script or the cache on the disk and this is not really a good idea in a lab where students have access to when they test some modules they code for our simulation...
Is there a way to encrypt the passwords stored in the cache with svn under linux?

Andreas Benzler

-- 
GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!
Jetzt dabei sein: http://www.shortview.de/?mc=sv_ext_mf@gmx
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org