Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58755
Return-Path: <keisial@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 46755 invoked from network); 7 Mar 2012 21:30:17 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 7 Mar 2012 21:30:17 -0000
Authentication-Results: pb1.pair.com smtp.mail=keisial@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=keisial@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.54 as permitted sender)
X-PHP-List-Original-Sender: keisial@gmail.com
X-Host-Fingerprint: 74.125.82.54 mail-ww0-f54.google.com  
Received: from [74.125.82.54] ([74.125.82.54:45177] helo=mail-ww0-f54.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 63/DA-15180-B53D75F4 for <internals@lists.php.net>; Wed, 07 Mar 2012 16:30:08 -0500
Received: by wgbdq13 with SMTP id dq13so5602047wgb.11
        for <internals@lists.php.net>; Wed, 07 Mar 2012 13:29:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        bh=I8qT7NMYEIuKJ/WZt84y2/92YbgAr7eqojSqQpQRv3A=;
        b=dy0Yzg1tZ1pti4/D88NVLq1NKQWGy1No+sYOONG8MYTjWgKyJ9G8eepy19ATNZSbud
         UPCOJDdo9PNnhNH1i3lpTjcJWFYm+5TLhlL+hftYujEXPDmVeNyVZbEBMH71co/faMWJ
         aQTpJ3s2oZI4gtFzLNCV9Gg3qC6FPMJqiClpC3cTE3sRAXhiYtqo7vB10pLNxJ2AAOIC
         hPb38gQ6t8tVaDDOV6AdPxaQh35HtN8wYq7kFewxAYIYLVewTm6MLy8YqHnNepRiM3N1
         8zd1lYGaI1fa2v8CMWjpkYMzJd88fW8tnBMSGtd8Oz3L0G+CtmpJdyqAy7wJVdaG2qZI
         Z2zQ==
Received: by 10.180.79.135 with SMTP id j7mr26018610wix.19.1331155798970;
        Wed, 07 Mar 2012 13:29:58 -0800 (PST)
Received: from [192.168.1.26] (89.Red-83-41-242.dynamicIP.rima-tde.net. [83.41.242.89])
        by mx.google.com with ESMTPS id ff2sm37086635wib.9.2012.03.07.13.29.56
        (version=SSLv3 cipher=OTHER);
        Wed, 07 Mar 2012 13:29:57 -0800 (PST)
Message-ID: <4F57D47E.1000804@gmail.com>
Date: Wed, 07 Mar 2012 22:34:54 +0100
User-Agent: Thunderbird
MIME-Version: 1.0
To: Adam Jon Richardson <adamjonr@gmail.com>
CC: "internals@lists.php.net" <internals@lists.php.net>
References: <CAJzDObekVt_F6JZP-B-YCs0khvfcSDW1PNeC6Bf5LUk=xPqVAQ@mail.gmail.com> <4F55DB1F.5040108@sugarcrm.com> <CAJzDObcwd6KMSNvJa8mui0QGiof+BEMoJ2WuGEq09uN+yc4n+g@mail.gmail.com> <4F567FD9.2050609@gmail.com> <CAJzDObcEUscO7q=h0DToEwvrxZMDnWFxjZnmWrsWxx+CKDkVxg@mail.gmail.com>
In-Reply-To: <CAJzDObcEUscO7q=h0DToEwvrxZMDnWFxjZnmWrsWxx+CKDkVxg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Providing sandboxed versions of include and require
 language constructs
From: keisial@gmail.com (=?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?=)

On 07/03/12 00:04, Adam Jon Richardson wrote:
> It would be the responsibility of the framework or CMS or application
> to protect against this type of attack (which they do quite well.)
> When you can force a plugin to work through your API, you can take
> appropriate measures. When the plugin can avoid working through, say,
> a file API that protects against misuse by using the internal file
> functions, this is a much more difficult issue to mitigate.
The key point is precisely, how do you ensure they can only call your API?