> Unfortunately, this is a long-standing security problem. It means that
> other non-suexec or user id "Apache" tools, such as Perl or PHP based
> modules, now have direct write access to your repository, now have
> arbitrary write access to the repository. In particular, they can
> directly do "r
> Do apache needs to have RW on /var/svn/disi/* ?
> for now it is user svn only
Yup, you got it.
Put your apache user into group svn. And give those rights recursive to
your repository directory.
drwxrwsr-x 7 apache svn . repository/
-fuz
> On Jan 12, 2011, at 08:12, Jehan PROCACCIA wrote:
>>> Ryan Schmidt wrote:
Remove the lines:
Alias /svn "/home/svn"
AllowOverride all
Apache is confused because you have told it you want it to serve /svn as
static
Original-Nachricht
> Le 12/01/2011 15:05, fuzzy_4711 a écrit :
>>> Remove the lines:
>>>
>>> Alias /svn "/home/svn"
>>>
>>> AllowOverride all
>>>
>>>
>
> Remove the lines:
>
>Alias /svn "/home/svn"
>
>AllowOverride all
>
>
> Apache is confused because you have told it you want it to serve /svn as
> static files located in /home/svn (the Alias directive and the /home/svn> section) and also that you want it
Hi,
it has been frustrating for me trying to set up my public available web
server to serve a svn repository also. I do not understand at all, what
happens, please help.
I am able to navigate with FF to https://devel.example.com/svn/test/
and see the "powered by Subversion version 1.6.6 (r40053)"
