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

Re: Subversion access control

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Wed, 20 Jul 2011 01:19:01 -0400

On Tue, Jul 19, 2011 at 11:14 PM, Andy Canfield
<andy.canfield_at_pimco.mobi> wrote:
> One thing has hit my mind today that I don't think you realize ...
>     I have never, in my entire life, seen a working Subversion system.
> Apparently Subversion, as distributed, doesn't work - the access
> authentications are deliberately turned off.

I'm afraid it depends on your access requirements. Seriously. Which
access technology are you using? svn+ssh (which I tend to recommend),
or Apache (using https://), or svn directorly (svn://) Start with that
and we'll walk you through it.

And please read the walkthroughs at http://svnbook.red-bean.com/,
which are pretty good, so we can help based on *which* approach you
want to use.

> It would be really neat if somebody had a sample repository on Linux in
> /var/svn and could tar it up and get it to me. Or zip it along with 'ls -l'
> output also. E-mail it or post it on the internet.
> I would like to see what the contents of server.conf and passwd and authz
> are IN AN ACTUAL WORKING SYSTEM. I would like to see what the file
> ownerships are and file access permisions. I could test this. I could make
> obvious changes to it ( e.g. user names) and it should continue to work.
> Having a working Subversion system I could then make small incremental
> changes to it and keeping it working.
> I would like to have a working system that I could break, rather than a
> broken system that I can't figure out how to fix.
> Thanks.
Received on 2011-07-20 07:19:49 CEST

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.