Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82065 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24277 invoked from network); 6 Feb 2015 19:46:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Feb 2015 19:46:55 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.53 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.192.53 mail-qg0-f53.google.com Received: from [209.85.192.53] ([209.85.192.53:42935] helo=mail-qg0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AE/01-19086-C2A15D45 for ; Fri, 06 Feb 2015 14:46:54 -0500 Received: by mail-qg0-f53.google.com with SMTP id f51so12923947qge.12 for ; Fri, 06 Feb 2015 11:46:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=pOKfVFfhVnSKlFajtzARyOZ5eBkrR3JP/DhufD2nqp4=; b=pqJeJrs77p4xmwrfYYHXuBUc5u5uTP2MiLSbL1jOEOdrf+n2pv434ESLmnmfLeySic qDMJsvdnv8MUr7ISXXN17WUa/akS+M0AggQnE9CU1hJyCpUiFkGB7aS3CjrB6gOuKF/2 arHlHlTlrvLLZ567keXnECvwQSb923UHMrQTBQwmy5Ox6umt4CF2CVqxWO9gy8oS5pnF JrbToBRIuWPtt/b0IWTT716LI6d4USOrBUfbCazPcAPnr+HeVJbB96kedqk0hId3RVJa mwBXuQDOr9U7il2IStJJr28HYwYjX3v0EdVUSEs+s/Wv21B7kCXskJpNs8kryqwzV10b vY+w== X-Received: by 10.224.22.72 with SMTP id m8mr7352789qab.66.1423252010122; Fri, 06 Feb 2015 11:46:50 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.229.28.72 with HTTP; Fri, 6 Feb 2015 11:46:09 -0800 (PST) In-Reply-To: References: Date: Sat, 7 Feb 2015 04:46:09 +0900 X-Google-Sender-Auth: ZHVSd94Zg0TEpxQzKxL1Y4l9naU Message-ID: To: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=089e0160c7107d6345050e70aef0 Subject: Re: [RFC][DISCUSSION] Introduce scrpt_path From: yohgaki@ohgaki.net (Yasuo Ohgaki) --089e0160c7107d6345050e70aef0 Content-Type: text/plain; charset=UTF-8 Hi all, On Fri, Feb 6, 2015 at 9:02 PM, Yasuo Ohgaki wrote: > This RFC was renamed from "script() and script_once()". > Original proposal had defect. It wasn't perfect. > > This RFC proposes "script_path" INI directive to eliminate > file/script inclusion at all via require(). > > https://wiki.php.net/rfc/script_path > > It's work in progress, but I would like to start discuss. > > I would like to know your preference. Multiple choices are OK ( +1 / -1 ) Comments are appreciated. 1. script_path INI. (Defines script path. Almost perfect solution with upload_path INI) [1] 2. upload_path INI. (Exception path in script_path. Protection against require('../../upload/evil');) [1] 3. require_embed INI (Enable/disable require()/require_once() embed(script only) mode. Temp INI) [2] 4. script()/script_once() [3] (No INI switch. Read only scripts. The same as require()/require_once(), require_embed=On ) 5. Leave as it is now (No protection against file inclusion & execution attacks.) [1] script_path defines script directory, upload_path defines exceptions under script_path. [2] require_embed is not described in current RFC. It's INI for enable/disable script only mode. require_embed should be REMOVED few years later. [3] script/script_once is not described in current RFC. It read/execute script only file. Thank you! Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --089e0160c7107d6345050e70aef0--