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

03/09/2006 05:20:02 AM	ktsys99 (at) kt-systems (dot) fi	Comment #3	Reply to this comment
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.

03/08/2006 03:34:20 PM	Chuck Hagenbuch	Version ⇒ HEAD Queue ⇒ Ingo

03/08/2006 03:33:57 PM	Chuck Hagenbuch	Comment #2 State ⇒ Not A Bug	Reply to this comment
What does this have to do with the horde.org systems? What do you expect to happen if your webserver can't read its own config files?

03/08/2006 11:12:36 AM	ktsys99 (at) kt-systems (dot) fi	Comment #1 State ⇒ Unconfirmed Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ ingo/config chmod problem Queue ⇒ Horde.org Servers	Reply to this comment
If using chmod go-rwx to ingo/config/ code brakes