<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Fri, 09 Jan 2009 06:14:54 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHP 10.0 Blog: php -T (variable tainting)]]></title>
      <guid>http://www.phpdeveloper.org/news/6862</guid>
      <link>http://www.phpdeveloper.org/news/6862</link>
      <description><![CDATA[<p>
On the PHP 10.0 Blog, there's <a href="http://php100.wordpress.com/2006/12/08/php-t/">a new post</a> today talking about variable tainting and what it might be like if PHP included it too.
</p>
<blockquote>
<a href="http://www.webreference.com/programming/perl/taint/">Perl</a> and <a href="http://www.rubycentral.com/book/taint.html">Ruby</a> have variable tainting. Maybe PHP should have it too?
</blockquote>
<p>
Variable tainting is a bit of built-in functionality that provides a "safety net" of sorts to the contents of variables to help protect both the users and the script itself from potentially harmful content.
</p>
<p>
He <a href="http://php100.wordpress.com/2006/12/08/php-t/">talks about</a> how Ruby and Perl handle the functionality and how, were PHP to work it in, which approach would fit better with PHP's current model:
</p>
<blockquote>
If one wants to implement proper tainting or sandboxing, it probably should be based on more generic approach that would account for existence of functions unknown in design time.
</blockquote>]]></description>
      <pubDate>Mon, 11 Dec 2006 10:26:00 -0600</pubDate>
    </item>
  </channel>
</rss>
