Re: Disabling PHP tags by php.ini and CLI options

From: Date: Tue, 10 Apr 2012 21:49:19 +0000
Subject: Re: Disabling PHP tags by php.ini and CLI options
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-59675@lists.php.net to get a copy of this message
Hi, It seems motivation of this RFC is better to be stated. Motivation to have this RFC is 1. "File Includes" is fatal security breach. 2. The reason why PHP is unsecure to "File Include" than other language is "Mandatory embed mode" 3. Non mandatory embed mode gives option users to better security. With this RFC, PHP could be as safe as other scripting languages with respect to file includes. This RFC is fully compatible with current code. Writing backward compatible code is as few as 3 lines. Most of security measures are not perfect solutions, but mitigation, just like canary and DEP. I suppose people who are concerned with security understand the value of these protections. Is there any good reasons not to have non mandatory embed mode as a additional security measure? Why not to make it harder for attackers to exploit? In short, I'm really annoyed to hear "PHP is insecure than Ruby/Perl/Python/etc" Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net

« previous php.internals (#59675) next »