On 8/4/05, André Pönitz <andre@wasy.de> wrote:
> > I have finally convinced my work to try a move from visual source safe
> > to subversion. At the moment we are simply accessing the subversion
> > repository using the file scheme and a shared drive (all windows
> > 2000). It seems that it would be better for us to run a svnserve
> > process, however the system admins are somewhat worried about running
> > servers. Our development team is at most 4 users so i was wondering
> > what risks we are running by not using svnserve or the apache module.
>
> What's the conceptional difference between a file server and a web
> server?
Well in my mind a single process is dealing with the subversion
repository so it can handle queueing request and transactions more
efficiently and safely than windows.
> If your admins are happy with serving files they should be happy
> with serving 'web pages' to the same set of clients.
They aren't. It thier minds they have accepted the security risk that
is running file shares but they have not accepted the risk that is
running apache or svnserve.
> Or do you want a security comparison between a locally used apache
> and a shared drive on Windows?
I would be interested in your thoughts. I know right now they are
very worried about who can administer the repository via svnadmin. Is
there any way to limit who can use the svnadmin command?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 4 16:02:38 2005