<?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>Wed, 22 May 2013 07:44:36 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Brian Swan's Blog: What's the Right Way to Prevent SQL Injection in PHP Scripts?]]></title>
      <guid>http://www.phpdeveloper.org/news/14140</guid>
      <link>http://www.phpdeveloper.org/news/14140</link>
      <description><![CDATA[<p>
<i>Brian Swan</i> has a new post today looking at one way you can protect your web application from potential attack - <a href="http://blogs.msdn.com/brian_swan/archive/2010/03/04/What_2700_s-the-right-way-to-avoid-SQL-injection-in-PHP-scripts_3F00_.aspx">preventing SQL injection</a> by filtering input.
</p>
<blockquote>
How to prevent SQL injection in PHP scripts is probably a topic that doesn't need anything more written about it. [...] However, it is important to have fresh information for new Web developers and I don't necessarily agree with some of the most common suggestions for preventing SQL injection. [...] So, this will be yet another post about preventing SQL injection, but I will offer my 2 cents about what I think is the right way to prevent it.
</blockquote>
<p>
He explains SQL injections for those that are unsure on the concept with a basic form example and what he thinks is a better way to prevent it than just trying to escape the SQL - bound parameters. These allow you to both filter and protect your application from any would-be attacks that might come your way. He is, of course, using SQL Server so the parameter binding is included in the database functionality. Other databases might have to use something like <a href="http://php.net/pdo">PDO</a> to accomplish the same kind of thing.
</p>]]></description>
      <pubDate>Fri, 05 Mar 2010 13:47:43 -0600</pubDate>
    </item>
  </channel>
</rss>
