> I'm wanting to set up networked subversion repositories. This is on > a > CentOS linux machine, I've got subversion 1.6.8 installed from rpm > package. > > Due to the access methods needed by my users svnserve would be the > best option. I've got the directory parent path /var/svn and under > that there's a repos# for each project where number is 1, 2, etc. > > I'm wanting to ensure encryption of data while traveling from the > server to the client so am looking in to cyrus-sasl, though not > finding what i'm looking for.
Wouldn't https:// be easiest? > I'm also needing to separate users. For example, user1 has access > to > only repos1 while user2 has only access to repos2 but not repos1. > Under their respective repos' each user can commit their own > projects > and manage them. You might want to look at subversion edge which I think sets all this up for you and gives you a web UI to set up users as well. > > I would have gone with an svn+ssh access, but don't want to give > out > system accounts, and none of my user's want their repos visible to > an > httpd server so apache is out. I don't think you need to give each user a system account. Wouldn't they all use the same account and you manage logins with keys? I'm not sure what that means? There needs to be a server apache or svnserve that access the repo. I'm not sure I see the difference if there is a security concern it is an issue with ACLs not what service is given the permissions. BOb
