Re: Run-time taint support proposal
| From: | Pierre | Date: | Wed, 20 Dec 2006 16:18:04 +0000 |
| Subject: | Re: Run-time taint support proposal | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-27149@lists.php.net to get a copy of this message | ||
On 12/20/06, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
Pierre wrote: I do not want the mode 3, for the reasons I explained earlier. I alsoIndeed, we have to keep them. It is somehow something I like to have (optionally), to be able to disable them, just like JIT or disable_functions. As a rule enforcement, it cannot be done in a better way :-). --PierreSame comment as before, drop all GPCES usages. This is a typical situtation, something like what Rasmus described in his post about Y! policy. Except we don't drop GPCES (well we do drop $_COOKIE, but for other reasons) which means that existing apps work fine. Dropping GPCES means it becomes very hard to run existing code. If the default filter is strict enough, I don't see the point in dropping those.Actually, I do. Especially if I had some legacy non-filtering application which I wanted to secure. I would prefer to break it hard and then assemble the pieces in the correct way, rather than play find-the-next-hole.