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

Re: Adding some security

From: Rob Brenart <svn_at_oculardata.com>
Date: 2006-12-06 11:45:07 CET

Andy Levy wrote:
> On 12/5/06, Rob Brenart <svn@oculardata.com> wrote:
>> Right now I have one repository I use, svn/src/ where I put all my
>> different projects.
>> I've recently started working with some outside contractors, and
>> obviously want to give them access to the code they need. However, I
>> don't want them to be able to download all of my source. At the least I
>> don't want them to be able to modify it all.
>> I'm using https for my access method.
>> Basically, when I want to add a new user, I just run the htpasswd2 -m
>> /path/to/.dav_svn.password username
>> and give them a password, and they're in.
>> So I have no idea where I'd go to limit things... advice?
> See
> http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.authz.perdir
Thanks, I read through that... and I get it all... turns out I was
already using the right apache modules (I had set this up awhile ago and
just had no recollection of setting those up, in part because it was so
long ago and in part because Debian helped a lot)

Anyway... I even understand the access files which I need to create,
which is really the crux of the whole thing. But what I'm not seeing is
where to put these files or what to call them. May seem trivial, and I'm
sure it is... but I can't seem to find it in the docs.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 6 11:45:46 2006

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.