Hanback, Phillip wrote:
> Good afternoon. I am an administrator in charge of a fairly large
> subversion environment. We normally access the repositories using Apache
> to serve on port 443. At this point in time, all of our servers are
> internal access only. Recently we’ve had a request to open up one of the
> repositories to a few developers outside of the company. There have been
> several strategies for accomplishing this goal. Security is of paramount
> importance. Some of the suggestions that have been tossed about are VPN
> access using firewall ACLs to limit access to only the required
> subversion server, setup of a new server supporting only the one repo
> and put it in the DMZ, one of the developers had suggested that the “old
> way” was to send tarballs of their code to be manually loaded into our
> internal subversion repo. To me this last option brings up questions of
> how to resolve conflicts in files normally decided by the developers.
> I’m just looking for some feedback from people with more subversion
> experience than me. Maybe one of you have had similar requests in the
> past and you could share your experience and wisdom on the subject. All
> responses appreciated. Thanks.
I've done this before and what we've done is set up another port on the server,
say 444, 8443 or something, and only set up a Location for that one repository.
The firewall would only forward packets to that port.
Regards,
Blair
--
Blair Zajac, Ph.D.
CTO, OrcaWare Technologies
<blair_at_orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2428050
Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-12-08 04:11:07 CET