Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74957 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45848 invoked from network); 17 Jun 2014 20:32:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Jun 2014 20:32:31 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.91 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.91 smtp91.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.91] ([108.166.43.91:35527] helo=smtp91.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 54/10-43470-CD5A0A35 for ; Tue, 17 Jun 2014 16:32:30 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp12.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id F0F72814F1; Tue, 17 Jun 2014 16:32:25 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp12.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 9D6E1816B5; Tue, 17 Jun 2014 16:32:25 -0400 (EDT) Message-ID: <53A0A5D9.9000509@sugarcrm.com> Date: Tue, 17 Jun 2014 13:32:25 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Pierre Joye , PHP internals References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP6, drop open_basedir? From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > On Windows f.e. it is very easy to create application pool with the > right users/permissions settings (IIS) or only permissions settings > (Apache). It is not possible to create one user per host on Apache > using mod_php but I think it is acceptable as it is mostly used as > development server or dedicated apps. This is not exactly true. Setups running multiple apps on mod_php/Apache are numerous. That said, open_basedir is not really a security feature meant to stop somebody with code execution access on the server. It's more of a safeguard feature - i.e. if somebody forgets to add check to some fopen, so that it may venture outside app space, open_basedir allows to implement such checks on a certain group of functions. I think it is a useful function, even though its framing in a security context makes it look like it does something that it can not do. It's like filters - very useful is some context but if you think you just slap a filter on your insecure code and get security=On then you're mistaken. So I don't think we need to remove this. I don't see a lot of maintenance problem with it as long as we use streams properly (and we should anyway) and we make it very clear what this tool actually does. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227