I had successfully chrooted my Apache 2 with mod_security, it run very
smoothly until I installed phpldapadmin (http://www.phpldapadmin.com,
a free LADP administrator's tool).
When I tried to login into phpldapadmin, it didnt response anything,
and when I looked at the error_log of httpd, it was something like
[Mon Jan 10 18:53:23 2005] [notice] child pid 19339 exit signal
Segmentation fault (11)
phpldapadmin runs without any problem if I dont use the chroot feature
of mod_security, my configuration is very simple:
# The name of the audit log file
I also get the nightly built version of mod_security but have no luck.
Please advise. Below are some information maybe useful:
[root@... apache2]# httpd -v
Server version: Apache/2.0.52
Server built: Oct 15 2004 11:39:29
[root@... apache2]# php -v
PHP 4.3.10 (cgi) (built: Dec 21 2004 10:27:48)
Copyright (c) 1997-2004 The PHP Group
Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies
From: Ivan Ristic <ivanr@we...> - 2005-01-10 13:06:11
Thai Duong wrote:
> Hello all,
> I had successfully chrooted my Apache 2 with mod_security, it run very
> smoothly until I installed phpldapadmin (http://www.phpldapadmin.com,
> a free LADP administrator's tool).
> When I tried to login into phpldapadmin, it didnt response anything,
> and when I looked at the error_log of httpd, it was something like
> [Mon Jan 10 18:53:23 2005] [notice] child pid 19339 exit signal
> Segmentation fault (11)
It's unlikely the crash has anything to do with modsecurity. It's
probably that phpldapadmin expects a file or device to always be
there and segfaults because the file is not available in the jail
(and there's no code to handle that eventuality).
You can probably find what file is causing the problems if you
strace the process as it crashes. When you do that you'll be able
to copy the file into jail to solve the problem.
I couldn't see from the web site whether phpldapadmin requires
some PHP extension to work with LDAP. Does it? If it does it's
probably the fault of the extension or the LDAP libraries it uses.
It's unlikely that a web-only application can cause a crash.
Ivan Ristic (http://www.modsecurity.org)