Encrypted passwords in conf/passwd ?

Hi all,

I understand that when I use the svn+ssh:// protocol, a new svnserve
process is launched within the ssh process, and it modifies the file
in the repository to make commits. Now, is it possible that two users
may commit via ssh at the same time, thus lauching two svnserve
processes, and creating race conditions to the repository files, and
corrupting them ?

This race condition happens when users access the repository via the
file:/// protocol, right ? Will it happen via svn+ssh:// too ?

I'm trying to switch to a single svnserve daemon process, and removing
direct access from the users to the repository files. Because it is a
single process handling every request, it can prevent race conditions.

My users are complaining about this change, because the passwd file in
the configuration files stores plain passwords (e.g. john =john123).
Instead, we would be much more confortable using hashes of passwords,
such as htpasswd, or the MD5 or the SHA1 of each password or any
encryption method.

It this possible ? Can this be done in svnserve ? Does Apache with
WebDAV allow this ?

[]'s
Leonel

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 1 20:12:57 2007