[PHP-BUG] Req #65026 [NEW]: if a function is used which is blocked by disable_functions nothing is logged

2013-06-13 Thread mbr at hlkomm dot de
From: mbr at hlkomm dot de Operating system: Irrelevant PHP version: Irrelevant Package: Testing related Bug Type: Feature/Change Request Bug description:if a function is used which is blocked by disable_functions nothing is logged Description

Bug #65026 [Nab]: if a function is used which is blocked by disable_functions nothing is logged

2013-06-13 Thread mbr at hlkomm dot de
Edit report at https://bugs.php.net/bug.php?id=65026edit=1 ID: 65026 User updated by:mbr at hlkomm dot de Reported by:mbr at hlkomm dot de Summary:if a function is used which is blocked by disable_functions nothing is logged Status

#13636 [Com]: configure doesn't find librecode

2003-03-10 Thread mbr at freebsd dot org
ID: 13636 Comment by: mbr at freebsd dot org Reported By: arne at dome dot net dot tw Status: Bogus Bug Type: Recode related Operating System: FreeBSD 4.1-RELEASE PHP Version: 4.0.6 New Comment: I have a fix for this. Please look at: http

#20661 [NEW]: Incorrectly identifies match

2002-11-26 Thread mbr
From: [EMAIL PROTECTED] Operating system: Linux redHat 7.0 and Solaris 8 PHP version: 4.2.3 PHP Bug Type: Regexps related Bug description: Incorrectly identifies match // finds 17 (also 15) but not 27 in option pattern see below if(ereg(5|7,17)){ print found;

#20190 [Com]: Random mem corruption: zend_get_executed_filename() mismatch

2002-11-14 Thread mbr
://people.freebsd.org/~mbr/patches/patch-main+fopen_wrappers.c The solution is quite easy. In the onyl case where the error happens, zend_get_executed_filename() is correct. and can be used. Since the error happens on perfect legitimate requests, which work most of the time, I don't think

#20190 [Com]: Random mem corruption: zend_get_executed_filename() mismatch

2002-11-14 Thread mbr
ID: 20190 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Critical Bug Type: Apache related Operating System: FreeBSD PHP Version: 4.3.0-dev New Comment: Hi, when this bug occurs, to confirm the wrong ini values?

#20211 [NEW]: Segfault in sapi_apache_header_handler

2002-11-01 Thread mbr
From: [EMAIL PROTECTED] Operating system: FreeBSD PHP version: 4CVS-2002-11-01 PHP Bug Type: Zlib Related Bug description: Segfault in sapi_apache_header_handler #0 0x2836810e in sapi_apache_header_handler (sapi_header=0xbfbff5e4, sapi_headers=0x2853c790) at mod_php4.c:259

#20211 [Com]: Segfault in sapi_apache_header_handler

2002-11-01 Thread mbr
ID: 20211 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Zlib Related Operating System: FreeBSD PHP Version: 4CVS-2002-11-01 New Comment: Looks like this one is related to: #19919 Previous Comments:

#19919 [Com]: segmentation violation in sapi_apache_header_handler, mod_php4.c line 208

2002-11-01 Thread mbr
ID: 19919 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Reproducible crash Operating System: FreeBSD 4.7 PHP Version: 4.2.3, 4.3.0-Dev New Comment: Hi all, I see this happen here too ... Also FreeBSD

#20190 [Com]: Random mem corruption: zend_get_executed_filename() mismatch

2002-11-01 Thread mbr
, the wrong random basedir message and the segfaults I encountered with my first two patches. http://people.freebsd.org/~mbr/patches/patch-main+fopen_wrappers.c The solution is quite easy. In the onyl case where the error happens, zend_get_executed_filename() is correct. and can be used. Since

#19292 [Com]: random error: open_basedir restriction in effect. File is in wrong directory

2002-10-31 Thread mbr
: open_basedir: File should be in /www/doc/www.customer.ch-80, but is in /www/doc/www.customer.org-80/photos/index.php file (/www/doc/www.aaa.ch-80/formmail.php) in Unknown on line 0 I added now both cases. Works so far :P but doesn't solve the real problem. http://people.freebsd.org/~mbr/patches

#20190 [NEW]: Random mem corruption: zend_get_executed_filename() mismatch

2002-10-31 Thread mbr
From: [EMAIL PROTECTED] Operating system: FreeBSD PHP version: 4.2.3 PHP Bug Type: Apache related Bug description: Random mem corruption: zend_get_executed_filename() mismatch I've done this change in main/fopen_wrappers.c to see what happens: - php_error(E_WARNING,

#20190 [Com]: Random mem corruption: zend_get_executed_filename() mismatch

2002-10-31 Thread mbr
ID: 20190 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Apache related Operating System: FreeBSD PHP Version: 4.2.3 New Comment: Note that this bug is similar to a other bug,

#20190 [Com]: Random mem corruption: zend_get_executed_filename() mismatch

2002-10-31 Thread mbr
ID: 20190 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Feedback Bug Type: Apache related Operating System: FreeBSD PHP Version: 4.2.3 New Comment: I already use this snapshot. And it still happens. I'll post soon

#20190 [Com]: Random mem corruption: zend_get_executed_filename() mismatch

2002-10-31 Thread mbr
ID: 20190 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Feedback Bug Type: Apache related Operating System: FreeBSD PHP Version: 4.2.3 New Comment: If I allow the open_basedir restriction to pass, I get now random

#20190 [Com]: Random mem corruption: zend_get_executed_filename() mismatch

2002-10-31 Thread mbr
ID: 20190 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Feedback Bug Type: Apache related Operating System: FreeBSD PHP Version: 4.2.3 New Comment: Previous dump was not the right one, sorry. I had dumps for children

#20190 [Com]: Random mem corruption: zend_get_executed_filename() mismatch

2002-10-31 Thread mbr
ID: 20190 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Feedback Bug Type: Apache related Operating System: FreeBSD PHP Version: 4.3.0-dev New Comment: Hi, should be critical, and now you say it's fixed. So what's

#20190 [Fbk-Opn]: Random mem corruption: zend_get_executed_filename() mismatch

2002-10-31 Thread mbr
ID: 20190 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Feedback +Status: Open Bug Type: Apache related Operating System: FreeBSD PHP Version: 4.3.0-dev New Comment: Ok, I think I'm a bit smarter now.

#20190 [Com]: Random mem corruption: zend_get_executed_filename() mismatch

2002-10-31 Thread mbr
ID: 20190 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Apache related Operating System: FreeBSD PHP Version: 4.3.0-dev New Comment: This is a example: Correct:

#20190 [Com]: Random mem corruption: zend_get_executed_filename() mismatch

2002-10-31 Thread mbr
ID: 20190 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Apache related Operating System: FreeBSD PHP Version: 4.3.0-dev New Comment: Sorry ... There is no /www/doc/www.bbb.imp.ch-80/html/visions/php

#20190 [Com]: Random mem corruption: zend_get_executed_filename() mismatch

2002-10-31 Thread mbr
ID: 20190 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Apache related Operating System: FreeBSD PHP Version: 4.3.0-dev New Comment: It looks to me that $path is composed somewhere. And a the old

#20190 [Com]: Random mem corruption: zend_get_executed_filename() mismatch

2002-10-31 Thread mbr
here now has solved both issues, the wrong random basedir message and the segfaults I encountered with my first two patches. http://people.freebsd.org/~mbr/patches/patch-main+fopen_wrappers.c The solution is quite easy. In the onyl case where the error happens, zend_get_executed_filename

#20190 [Com]: Random mem corruption: zend_get_executed_filename() mismatch

2002-10-31 Thread mbr
/~mbr/patches/patch-main+fopen_wrappers.c The solution is quite easy. In the onyl case where the error happens, zend_get_executed_filename() is correct. and can be used. Since the error happens on perfect legitimate requests, which work most of the time, I don't think this is a security risk

#19292 [Com]: random error: open_basedir restriction in effect. File is in wrong directory

2002-10-24 Thread mbr
ID: 19292 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Feedback Bug Type: Apache related Operating System: linux PHP Version: 4.3.0-dev,4.2.3 New Comment: I changed the random message: PHP Warning: open_basedir

#19292 [Com]: random error: open_basedir restriction in effect. File is in wrong directory

2002-10-24 Thread mbr
ID: 19292 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Feedback Bug Type: Apache related Operating System: linux PHP Version: 4.3.0-dev,4.2.3 New Comment: I'm using this workaround for now. It solves the problem:

#19292 [Com]: random error: open_basedir restriction in effect. File is in wrong directory

2002-10-24 Thread mbr
/~mbr/patches/fopen_wrappers.c.diff Previous Comments: [2002-10-24 04:26:38] [EMAIL PROTECTED] I'm using this workaround for now. It solves the problem: --- main/fopen_wrappers.c.orig Wed Oct 23 11:49:40 2002 +++ main