From: L. Christopher Luther <CLuther@Xybernaut.com> - 2004-01-28 19:23:31
In answer to (1): The problem is that the MySQL library functions in PHP
are configured to connect to "localhost", which means using the socket file
created by the local MySQL process. And since the socket file is outside of
the SecChrootDir "jail", it cannot be "seen" by the PHP code.
I too has this problem when I used SecChrootDir, and all I needed to do was
configure the PHP code on my Apache server to use "127.0.0.1" instead of
"localhost", which forces the PHP MySQL libraries to use TCP instead of the
local socket file.
I also had to tweak the MySQL user accounts to accept connections from
"userid@...", which is the name that the 127.0.0.1 IP
address resolves to.
From: Bart [mailto:bart@...]
Sent: Monday, January 26, 2004 2:52 AM
Subject: [mod-security-users] chroot and other problems
I chrooted apache in standard way. There was no problem.
Then I used mod_security to chroot "normal" apache I set in httpd.conf
but Apache return error
no mysql.sock in /var/lib/mysql/mysql.sock
cant write to /tmp/ ...
The file mysql.sock exists and /tmp/ has 777 rights.
Where is the problem?
Can I use mail() php function with mod_security chrooted apache?
It was major problem that I decided no tto use chrooted apache
Additionaly I would like to test mod_security at all without chroot
I added this config to my httpd.conf
After restarting apache I cant logon with my authentication php script.
I use session().
How to resolve this.
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
mod-security-users mailing list