Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:46017
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 209.85.219.227 cause and error)
Message-ID: <4AFA0449.2030600@chiaraquartet.net>
Date: Tue, 10 Nov 2009 18:24:41 -0600
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070807)
MIME-Version: 1.0
To: Stanislav Malyshev <stas@zend.com>
CC:  internals@lists.php.net, Christian Schneider <cschneid@cschneid.com>, 
 Lukas Kahwe Smith <mls@pooteeweet.org>
References: <413588E2-8AC8-49F7-B7BF-97BEFB0A71E4@pooteeweet.org> <4AF9A03E.8000207@cschneid.com> <4AF9AE1A.9000005@zend.com> <4AF9C589.3090604@chiaraquartet.net> <4AF9CCEA.1030500@zend.com>
In-Reply-To: <4AF9CCEA.1030500@zend.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: alternative to the fopen() hack in autoloaders
From: greg@chiaraquartet.net (Greg Beaver)

Stanislav Malyshev wrote:
> Hi!
>
>>> This would break security distinction between file ops and include ops,
>>> when URLs are allowed for open but not include.
>
> Additional thing - it probably would be a problem for bytecode caches,
> since they'd have to:
> a. watch all file opens, in case some of these will later be used for
> include
> b. somehow be able to get filename back from open stream to get the
> cached file.
Hi again,

A good point.  Fortunately, most streams do store the filename in the
stream struct, so this would still probably be possible in the majority
of cases.  If not available, the original requested filename is used
(the one from the fopen call), so opcode caches probably could just use
that.

Greg