Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I need to setup several services in a Linux VPS and want to use system accounts for managing authentication/authorization on those services.

When I setting up a svn server I did something like this, which basically creates a new group for each repository and when the administrator wants to give write access to a user it is only a matter of adding that user to the repository group. The problem with this setup is that users of the repository group are not limited to writing to the repository via the svnserve interface, and can also modify the repository physical directory directly(possible corrupting the repository).

Another solution is to use Apache as an interface for svn, without giving users write permissions to the repository files, but then I would loose the ease of administration via unix accounts/groups.

Is there any way to setup an SVN Server to use unix accounts for authentication/authorization without giving the users physical access to the repository physical directory?

share|improve this question
up vote 2 down vote accepted

Simon Tatham's article My Experiences With Subversion suggests creating a separate account for svnserve and allowing people to use it through userv. (Alternatively, sudo can be configured in a similar manner.)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.