[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn+ssh vs. https (different access methods)

From: <d.guthmann_at_gmx.net>
Date: Thu, 09 Feb 2012 10:15:37 +0100


first of all: I'm really sorry for the missing subject-line.

-------- original message --------
> Will it stay with access on the repositories only or is it will your
> external devs need access to test infrastructure, documentation or
> whatever, too? In the latter case I would prefer setting up a proper
> VPN infrastructure which allows you to use Apache as the svn host for
> your external devs and only let them see specific networks they need
> via routing, firewall etc.

Normally I would agree to you, but it would be too extensive to gave only to that part of our network, which is necessary for that project, when using a VPN-Client. So the VPN-Connection would be restricted only to the Subversion-Service, so I seems to be easier to set up a SSH-Tunnel than a VPN-Service.

A better solution would be a kind of proxy-service that I can place in the DMZ... is there a working proxy-solution for subversion?
Some time ago I've gave access to a subversion-repository via a reverse-proxy running on apache... that wasn't working properly...
Are there other proxy-like services which will work well with subversion?



Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
Received on 2012-02-09 10:16:26 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.