Req #54239 [Opn->Sus]: disable_functions tightening like open_basedir

Edit report at https://bugs.php.net/bug.php?id=54239&edit=1 ID: 54239 Updated by: cmb@php.net Reported by: naox at o2 dot pl Summary: disable_functions tightening like open_basedir -Status: Open +Status: Suspended Type: Feature/Change Request Package: PHP options/info functions PHP Version: 5.3.6 Block user comment: N Private report: N New Comment: This feature requires discussion for which this bug tracker is unsuitable. If anybody is still interested in this, please forward the request to the internals mailing list[1]. For the time being, I'm suspending this ticket. [1] <https://www.php.net/mailing-lists.php#internals> Previous Comments: ------------------------------------------------------------------------ [2013-08-03 15:55:54] ben dot rubson at gmail dot com See summary bug #65386 ------------------------------------------------------------------------ [2011-04-26 05:38:47] fg345twrg at gmail dot com Making disable_functions INI_ALL and allowing it to set only if previously empty would be good start. Tightening would be perfect. ------------------------------------------------------------------------ [2011-04-26 00:30:54] naox at o2 dot pl allow disable_functions tightening like open_basedir :( ------------------------------------------------------------------------ [2011-03-13 05:33:28] naox at o2 dot pl Description: ------------ http://php.net/manual/en/ini.core.php disable_functions is php.ini only open_basedir is PHP_INI_ALL - because next change can only append to open_basedir path, never take something back. Disable_functions should work the same way! It should be PHP_INI_ALL and allowing adding functions, but never taking those back. This allong open_basedir and prepend could make handy to make privledge separation for multiple sites but wihtout multiple php.ini ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=54239&edit=1