permissions and self-signed ssl keys for access

[dave <dm...@woh.rr.com>]

Hello,
    I've been using svn for a while for local projects. Lately i've been
busy but have finally got back to this, i have to now network my server. I'm
using FreeBSD 5.3 and apache2. I've set up a repository and given it owner
and group of www which the apache user runs as. What i'd like to do is
create a repository, all of which are under a specific area, and have
permissions and group ownerships asigned automatically. I'm going to be
creating several dozen repositories and manually changing everything could
get tedious. I've set up blanket access control for write access and
anonymous users can do readonly operations, but for transmitting passwords
i'd like to have that done over ssl so the password is not cleartext.
Thanks.
Dave.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: permissions and self-signed ssl keys for access

[Chris Rose <of...@gmail.com>]

You and me both :)

I think that you're describing precisely the setup I fought tooth and
nail to get working on this end.  I had the additional problem,
though, of wanting to keep the repository open to my login user as
well for file:// access.

Here's a rough outline of what I had to do, but you'll want to do some
googling to go with it.

First:  I have a repository directory under $HOME (your mileage may
vary).  This directory, call it $REPOBASE, is where all of my various
repositories go.  So, in it I have $REPOBASE/repo1, $REPOBASE/repo2,
&c.

This is set to my-user:www-user, permissions drwsrwsr-t

Each repository subdirectory in it is created with just 

$ svnadmin create $REPOBASE/repo-new

and then I have to do

$ chmod -R g+w $REPOBASE/repo-new

This allows the www-user access.  However, if the user for the
repository was www-user as well, then it would not be necessary.

As far as the Apache setup goes, just follow the red book.  It's
pretty simple to make it work without SSL, I had that part up and
running as soon as I worked out the permissions issue.

To set up apache for ssl access is easily the hardest part.  I'd offer
to help, but I still get flashbacks :)  That, and I don't remember the
specific steps.  Another reader of this list is writing a book on SVN
and has some amazingly helpful information in one of the appendices on
the subject, it's what I used.  Perhaps he'll send you those.

On Fri, 11 Feb 2005 12:18:38 -0500, dave <dm...@woh.rr.com> wrote:
> Hello,
>     I've been using svn for a while for local projects. Lately i've been
> busy but have finally got back to this, i have to now network my server. I'm
> using FreeBSD 5.3 and apache2. I've set up a repository and given it owner
> and group of www which the apache user runs as. What i'd like to do is
> create a repository, all of which are under a specific area, and have
> permissions and group ownerships asigned automatically. I'm going to be
> creating several dozen repositories and manually changing everything could
> get tedious. I've set up blanket access control for write access and
> anonymous users can do readonly operations, but for transmitting passwords
> i'd like to have that done over ssl so the password is not cleartext.
> Thanks.
> Dave.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
> 
> 


-- 
Chris R.
======
Not to be taken literally, internally, or seriously.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org