<?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>Tue, 18 Jun 2013 18:41:35 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHP 10.0 Blog: Production mode]]></title>
      <guid>http://www.phpdeveloper.org/news/6911</guid>
      <link>http://www.phpdeveloper.org/news/6911</link>
      <description><![CDATA[<p>
In an effort to get some thought going about ways to encourage security in PHP applications, <i>Stas</i> has posted <a href="http://php100.wordpress.com/2006/12/17/production-mode/">an idea</a> about a simplified php.ini setting - production=On.
</p>
<p>
His idea is that, with this setting on, the PHP installation would:
<ul> 
<li>disable display errors
<li>disable phpinfo()
<li>turn expose_php off
<li>make max_execution_time/memory_limit reasonable
<li>and possibly a few others that some developers forget to set correctly
</ul>
<a href="http://php100.wordpress.com/2006/12/17/production-mode/">Comments on the post</a> range from disagreement to suggestions on improvement and support.
</p>]]></description>
      <pubDate>Mon, 18 Dec 2006 08:43:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[PHP Security Blog: A Trio of Javascript Issues]]></title>
      <guid>http://www.phpdeveloper.org/news/6810</guid>
      <link>http://www.phpdeveloper.org/news/6810</link>
      <description><![CDATA[<p>
On the PHP Security Blog, there's three new posts that <i>Stefan Esser</i> has written up that demonstrate some of the more destructive uses of Javascript that he's found:
<ul>
<li><a href="http://blog.php-security.org/archives/54-JavaScriptHTML-Portscanning-and-HTTP-Auth.html">JavaScript/HTML Portscanning and HTTP Auth</a>
<li><a href="http://blog.php-security.org/archives/56-Bruteforcing-HTTP-Auth-in-Firefox-with-JavaScript.html">Bruteforcing HTTP Auth in Firefox with JavaScript</a>
<li><a href="http://blog.php-security.org/archives/55-JavaScript-Scanning-and-expose_phpOn.html">JavaScript Scanning and expose_php=On</a>
</ul>
</p>
<p>
While the first two are interesting, it's the last of these that most directly applies to PHP. He gives a simple "proof of concept" that checks to see if the embedded image is the correct "size" to be related to a webserver running PHP with the expose_php setting set to "on".
</p>]]></description>
      <pubDate>Fri, 01 Dec 2006 13:22:28 -0600</pubDate>
    </item>
  </channel>
</rss>
