Re: Run-time taint support proposal
| From: | Lukas Kahwe Smith | Date: | Wed, 20 Dec 2006 10:03:42 +0000 |
| Subject: | Re: Run-time taint support proposal | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-27143@lists.php.net to get a copy of this message | ||
Stanislav Malyshev wrote:
I disagree - you describe scenario where the user chooses to insufficiently or wrongly sanitize the data, and since tainting can not protect from it you say tainting is not useful. However, as I already said, tainting is not supposed to do that. It's like blaming computer OS for not preventing somebody from stealing the laptop with it :) Tainting IS NOT supposed to cure all your security problems. It is supposed to help YOU deal with some of them.No I describe an approach to work around the lack of context aware tainting in which you always work with the initial input in each of the context. However as I describe it means you need to apply any data massaing twice in this case. This is just as error prone as forgetting about escaping user input without taint. As a result you simply trade one error class with another one, while introducing additional complexity. regards, Lukas