user auth with svn+ssh access on shared hosting inadequate

My personal hosting only allows a single shell account which is
troublesome when I would like multiple developers contributing to a
repository.

My current solution is such:
Genereate private/public key pairs using ssh-keygen
Modify .ssh/authorized_keys, adding for each developer needed,
command="~/svn/bin/svnserve -t -r ~/svn/repos/
--tunnel-user=author_name" (that user's associated public key)

Though this works it's bothersome if users are to be added.

The ideal situation for me would be to have a switch enabling the
daemon-style auth (password-db) when tunneling.

Is my situation rare enough that such a request isn't valid?

It is two layers of auth but I think most people restricted to a
single shell account would happily use it.

Criticism? (other than telling me to get a better host =)

Travis

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 27 05:55:55 2005