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

Re: Needed 'chmod 777' to allow remote commit via http ?

From: Alex <xlegion_at_gmail.com>
Date: 2006-04-17 09:54:19 CEST

On 4/16/06, Bruno Costacurta <cob1@biz.tiscali.be> wrote:
>
> Hello To All,
> do I need a 'chmod -R 777 /usr/local/svn/' to allow access from remote
> client ?
>
> I setup Apache2 and related files.
> Everything works from remote access via http (ie. http://..etc.. and svn
> checkout http://..etc.. are ok from remote PC)
> but I was not able to commit files because of permission denied on
> directory ../db/transactions/*
>
> I resolved this via a chmod -R 777.
> But is this mandatory ? chmod 777 is not secure and would like to avoid.
> How to proceed ?
>
> My config:
> file httpd.conf:
> ...
> <Location /usr/local/svn/repos/documents>
> DAV svn
> SVNPath /usr/local/svn/repos/documents
> AuthType Basic
> AuthName "Subversion Repository"
> AuthUserFile /etc/httpd/passwd/passwords
> AuthzSVNAccessFile /etc/httpd/passwd/svnauthz.conf
> Require valid-user
> </Location>
> ...
>
> file passwords :
> [/]
> bruno = rw
>
>
> Thanks for attention.
> Bye,
> Bruno
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
You need to allow the Apache process read/write access to the repository.
The best way to achive that is to create a group called SVN and add Apache's
runtime user to that group. Then change the group for the repository to SVN
and set write access for the group.
Received on Mon Apr 17 09:55:29 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.