On 11/15/2009 3:10 PM, dale wrote:
> I'm want to have a very locked down server with just one linux login
> shared by all developers (Windows / Tortoise). I found Bodhi's write-
> up here http://blog.bodhizazen.net/linux/svnssh/comment-page-1/#comment-1270
> But I'm having trouble getting it to work with Tortoise vs. a Windows
> Collabnet svn shell client.
> Anyone else successfully done something like this? If so, any
> pointers to how?
> NOTE: I know how to use Tortoise and ssh--the trick that's not
> working is how to get multiple front-end users tunneled through one
> server login and still preserve their svn identity in subversion write
It's also mentioned in the SVN Book.
It's also possible to have multiple users share a single account.
Instead of creating a separate system account for each user, generate a
public/private key pair for each person. Then place each public key into
the authorized_users file, one per line, and use the --tunnel-user option:
TYPE1 KEY1 harry_at_example.com
TYPE2 KEY2 sally_at_example.com
One personal note... I prefer to use a full path for the svnserve
executable (such as /usr/bin/svnserve), which forces SSH to use the
svnserve executable in the /usr/bin folder intead of searching the PATH.
We also use the "-r /var/svn" option for svnserve, so that our svn+ssh
URLs show up with the SVN repository as the root level. It's the
While we don't do multiple users piped into a single server-side
account, we do use both TortoiseSVN and CollabNet's SVN client using
svn+ssh with public key authentication here. The private keys are loaded
into Pageant and we configure a PuTTY session (because we run SSH on a
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-11-16 22:10:12 CET