[Tickets #3577] RESOLVED: ingo/config chmod problem

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=3577
-----------------------------------------------------------------------
 Ticket             | 3577
 Updated By         | ktsys99 at kt-systems.fi
 Summary            | ingo/config chmod problem
 Queue              | Ingo
 Version            | HEAD
 State              | Bogus
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


ktsys99 at kt-systems.fi (2006-03-08 21:20) wrote:

This is copy of your own security and installation docs at
http://www.horde.org/horde/docs/?f=SECURITY.html
""""""""""""""""""""""""""""""""""""""""
If you use a Unix system, one way to make the configuration files and
directories accessible only to the web server is as follows. Here we assume
that the web server runs as the user apache and the files are located in
/home/httpd/html -- substitute the correct user or file path if needed:

$ chown -R apache /home/httpd/html/horde/config
$ chown -R apache /home/httpd/html/horde/*/config
$ chmod -R go-rwx /home/httpd/html/horde/config
$ chmod -R go-rwx /home/httpd/html/horde/*/config

"""""""""""""""""""""""""""""""""""""""""""""""""""""""

Only ingo seems to break for that.