<?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>Sun, 26 May 2013 03:28:39 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[John Cox's Blog:  Security Blunders]]></title>
      <guid>http://www.phpdeveloper.org/news/4533</guid>
      <link>http://www.phpdeveloper.org/news/4533</link>
      <description><![CDATA[In <a href="http://wyome.com/index.php?module=articles&func=display&ptid=10&aid=492">his latest post</a> today, <i>John Cox</i> takes a look at one of the latest posts from the SitePoint PHP blog - the <a href="http://www.sitepoint.com/article/php-security-blunders">Top 7 PHP Security Blunders</a>.
<p>
<quote>
<i>
This morning I read the <a href="http://www.sitepoint.com/article/php-security-blunders">Top 7 PHP Security Blunders</a> which contained (at least in my mind) a few questionable comments about PHP security. Luckily for the early readers of the article, there was a very long comment by <a href="http://shiflett.org/>Chris Shiflett</a> trailing the article. The <a href="http://www.sitepoint.com/forums/showpost.php?p=2374757&postcount=9">comments</a> were a very nice critique of the article which also corrects a few obvious mistakes within the article itself. 
<p>
The comments have now been pushed off the main article to the forum, (which is a shame) but as a developer, you would be doing yourself a disservice by not also taking the time to read the counter-point. They are insightful without being inflammatory.
</i>
</quote>
<p>
The comments by <i>Chris</i> that he makes reference to can be found <a href="http://www.sitepoint.com/forums/showpost.php?p=2374757&postcount=9">here in the SitePoint forums</a>...]]></description>
      <pubDate>Wed, 21 Dec 2005 07:08:07 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[SitePoint PHP Blog: Top 7 PHP Security Blunders]]></title>
      <guid>http://www.phpdeveloper.org/news/4532</guid>
      <link>http://www.phpdeveloper.org/news/4532</link>
      <description><![CDATA[On the SitePoint PHP blog today, <i>Pax Dickinson</i> shares with us the "Top 7 PHP Security Blunders" as he sees them.
<p>
<quote>
<i>
In this article, I'll detail many of the common PHP programming mistakes that can result in security holes. By showing you what not to do, and how each particular flaw can be exploited, I hope that you'll understand not just how to avoid these particular mistakes, but also why they result in security vulnerabilities. Understanding each possible flaw will help you avoid making the same mistakes in your PHP applications.
</i>
</quote>
<p>
<a href="http://www.sitepoint.com/article/php-security-blunders">His list</a> includes:
<ul>
<li>Unvalidated Input Errors
<li>Access Control Flaws
<li>Cross Site Scripting (XSS) Flaws
<li>Data Handling Errors
</ul>
<p>
There's more listed, so be sure to check out the rest of the article - each item is explained and on some, sample code is included where it makes sense...]]></description>
      <pubDate>Wed, 21 Dec 2005 07:04:07 -0600</pubDate>
    </item>
  </channel>
</rss>
