Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37183
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.142.191 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=prXTlMKUrGbIqiIuLUt3Xogk3Oi/2jEYdnLXWAVGX4jDioo7bUqLljZ3GtStzP8VGfbi9uHcC0b969VLCQ8jMDeZ+BtnmYN/KOLixBiF5Fyhkh6Hdx4pnYp7P50VZ1hQ59cFusO6w9XsCzX/c6/LBFtxLu/h2X5eHXMdYxSWCbk=
Message-ID: <78c6bd860804221129u19803acaw26e2cb02c6cfc660@mail.gmail.com>
Date: Tue, 22 Apr 2008 14:29:23 -0400
To: internals@lists.php.net
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: zval taint bits
From: ioplex@gmail.com ("Michael B Allen")

Hi,

I saw Wietse's taint presentation at nyphp last night and I just
wanted to express my support for the feature.

It seems to me OR-ing bits together between zval fields is relatively
harmless. Clearly it will not catch everything as extensions can
introduce clean zvals that are in fact tainted (or visa versa) but I
foresee that this feature would amount to adding a very informative
warning for developers. Just as you would get a warning for trying to
call a function with the wrong parameters or divide by zero, the taint
bits can be used to teach developers as to how to properly process
their data.

Mike

PS: I am strongly against the idea of filters - the application should
output what I tell it to output and nothing else.