#23942 [Opn->Fbk]: php 4.3.x causes apache2+mod_ssl to sigsev on client authentication

ID: 23942 Updated by: sniper@php.net Reported By: alextxm at tin dot it -Status: Open +Status: Feedback Bug Type: Apache2 related Operating System: Linux PHP Version: 4.3.2 New Comment: What was the configure line used to configure PHP? And are you sure you're linking both apache2 and PHP with _same_ SSL libs? Previous Comments: ------------------------------------------------------------------------ [2003-06-01 17:35:22] alextxm at tin dot it i'm going to rebuild php with --enable-debug and to try to get some backtraces. btw, please note that the no php scripts are actually involved in this scenario: the website i'm testing it on has no php script. I simply try to access an area (with plain html pages) which requires me to have a SSL Client Certificate; authentication (and so, access) happens only if apache2 (i'm using 2.0.46) is started without -D PHP4 otherwise authentication fails and the apache error log file only says: "[Mon Jun 02 00:15:54 2003] [notice] child pid 16784 exit signal Segmentation fault (11)" ------------------------------------------------------------------------ [2003-06-01 17:24:41] derick@php.net Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php Once you have generated a backtrace, please submit it to this bug report and change the status back to "Open". Thank you for helping us make PHP better. ------------------------------------------------------------------------ [2003-06-01 17:19:09] alextxm at tin dot it Client authentication with a SSL certificate work fine in apache2 until php4 is loaded as a module. trying to access an area granted only with a client-certificate based authentication with php4 enabled as module will cause Apache2 to sigsev (Segmentation Fault) in the related child process(es). Disabling php4 will cause the problem to disappear, so I guess it really is a php related problem. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=23942&edit=1