On Dec 5, 2004, at 11:26 AM, Ben Collins-Sussman wrote:
>
> On Dec 5, 2004, at 10:09 AM, Gili wrote:
>
>> Isn't there a way for us to do this?
>>
>> 1) SSH server and Subversion server running in deamon mode
>> 2) User connects to the server using SSH client
>> 3) User invokes svn client operations on the remote connection
>>
>>
>
> Sure there is. Start 'svnserve -d' on a server behind some firewall,
> then have all your users set up ssh-encrypted 'tunnels' through the
> firewall, to port 3690 on your server. This ssh tunnelling technique
> works for essentially every server-process in the universe; it's not
> an svn-specific solution at all. It's described in this FAQ:
>
> http://subversion.tigris.org/project_faq.html#paranoid
>
> of course, the annoyance with this is (1) teaching your users to set
> up tunnels with 'ssh -L', (2) being prompted for BOTH ssh and svnserve
> authentication.
I do exactly this and find it very simple. I have a simple batch file
to set up the tunnel and svn caches the svnserve authentication info,
so I only need to enter it once. It isn't that annoying. I run the
batch file, work with subversion, and then terminate the command window
corresponding to the ssh tunnel when I'm done.
I am using SSH to tunnel through the firewall for other reasons as well
(like using remote desktop), so it is no big deal.
I also edit the hosts file so that svn:externals resolves the machine
name in the URL to 127.0.0.1 and it all runs smoothly.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Dec 5 22:58:56 2004