<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Three Important Tips to Write PHP Code Defensively</title>
	<atom:link href="http://www.brownphp.com/2008/12/three-important-tips-to-write-php-code-defensively/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brownphp.com/2008/12/three-important-tips-to-write-php-code-defensively/</link>
	<description>Created and Designed for Object Oriented PHP and Web Developers</description>
	<lastBuildDate>Wed, 23 Nov 2011 08:18:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Matilde Gasmen</title>
		<link>http://www.brownphp.com/2008/12/three-important-tips-to-write-php-code-defensively/comment-page-1/#comment-16789</link>
		<dc:creator>Matilde Gasmen</dc:creator>
		<pubDate>Tue, 14 Jun 2011 22:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownphp.com/?p=39#comment-16789</guid>
		<description>&lt;strong&gt;Sala de leos...&lt;/strong&gt;

http://www.projetomodernodacozinha.com paisagismo e mobiliário de design...</description>
		<content:encoded><![CDATA[<p><strong>Sala de leos&#8230;</strong></p>
<p><a href="http://www.projetomodernodacozinha.com" rel="nofollow">http://www.projetomodernodacozinha.com</a> paisagismo e mobiliário de design&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 45 Must Read PHP Articles and Resources</title>
		<link>http://www.brownphp.com/2008/12/three-important-tips-to-write-php-code-defensively/comment-page-1/#comment-3326</link>
		<dc:creator>45 Must Read PHP Articles and Resources</dc:creator>
		<pubDate>Fri, 08 Jan 2010 17:42:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownphp.com/?p=39#comment-3326</guid>
		<description>[...] Three Important Tips to Write PHP Code Defensively [...]</description>
		<content:encoded><![CDATA[<p>[...] Three Important Tips to Write PHP Code Defensively [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Super Star &#187; Blog Archive &#187; PHP Articles and Resources for all levels</title>
		<link>http://www.brownphp.com/2008/12/three-important-tips-to-write-php-code-defensively/comment-page-1/#comment-2525</link>
		<dc:creator>Web Super Star &#187; Blog Archive &#187; PHP Articles and Resources for all levels</dc:creator>
		<pubDate>Tue, 23 Jun 2009 06:53:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownphp.com/?p=39#comment-2525</guid>
		<description>[...] Three Important Tips to Write PHP Code Defensively [...]</description>
		<content:encoded><![CDATA[<p>[...] Three Important Tips to Write PHP Code Defensively [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 43 Must Read PHP Articles and Resources &#124; Hi, I'm Grace Smith</title>
		<link>http://www.brownphp.com/2008/12/three-important-tips-to-write-php-code-defensively/comment-page-1/#comment-2524</link>
		<dc:creator>43 Must Read PHP Articles and Resources &#124; Hi, I'm Grace Smith</dc:creator>
		<pubDate>Fri, 19 Jun 2009 15:37:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownphp.com/?p=39#comment-2524</guid>
		<description>[...] Three Important Tips to Write PHP Code Defensively [...]</description>
		<content:encoded><![CDATA[<p>[...] Three Important Tips to Write PHP Code Defensively [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tagz &#124; &#34;Three Important Tips to Write PHP Code Defensively : Brown PHP&#34; &#124; Comments</title>
		<link>http://www.brownphp.com/2008/12/three-important-tips-to-write-php-code-defensively/comment-page-1/#comment-2510</link>
		<dc:creator>Tagz &#124; &#34;Three Important Tips to Write PHP Code Defensively : Brown PHP&#34; &#124; Comments</dc:creator>
		<pubDate>Sat, 16 May 2009 16:54:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownphp.com/?p=39#comment-2510</guid>
		<description>[...]               [upmod] [downmod]     Three Important Tips to Write PHP Code Defensively : Brown PHP  (brownphp.com)    0 points posted 4 months, 3 weeks ago by trshant  tags 4mdelicious security php  [...]</description>
		<content:encoded><![CDATA[<p>[...]               [upmod] [downmod]     Three Important Tips to Write PHP Code Defensively : Brown PHP  (brownphp.com)    0 points posted 4 months, 3 weeks ago by trshant  tags 4mdelicious security php  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mario</title>
		<link>http://www.brownphp.com/2008/12/three-important-tips-to-write-php-code-defensively/comment-page-1/#comment-509</link>
		<dc:creator>mario</dc:creator>
		<pubDate>Sun, 04 Jan 2009 00:56:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownphp.com/?p=39#comment-509</guid>
		<description>SQL escaping is not a solution. The problem with PHP is, that people concatenate strings to build up SQL queries. It&#039;s the most obvious thing to do in a scripting language making this easy. It&#039;s also fundamentally flawed.

A “mysql_real_escape_string” is easily forgotten. All SQL exploits in the various PHP applications can be attributed to &quot;Oooops, sorry. Forgot to escape! [Again]&quot;

In other languages, like Java or C, this doesn&#039;t happen that frequently. They&#039;re not prone to the SQL string concatenation trap. They just use &quot;parameterized SQL&quot;.

Parameterized SQL is available in PHP too. You can have bind variables and ? placeholders with PDO for example.

That&#039;s the only solution worth recommending. Mentioning _escape() for the fivemillionandthwohundredthirtythousandandfiftysecond time OTH won&#039;t do much good.</description>
		<content:encoded><![CDATA[<p>SQL escaping is not a solution. The problem with PHP is, that people concatenate strings to build up SQL queries. It&#8217;s the most obvious thing to do in a scripting language making this easy. It&#8217;s also fundamentally flawed.</p>
<p>A “mysql_real_escape_string” is easily forgotten. All SQL exploits in the various PHP applications can be attributed to &#8220;Oooops, sorry. Forgot to escape! [Again]&#8221;</p>
<p>In other languages, like Java or C, this doesn&#8217;t happen that frequently. They&#8217;re not prone to the SQL string concatenation trap. They just use &#8220;parameterized SQL&#8221;.</p>
<p>Parameterized SQL is available in PHP too. You can have bind variables and ? placeholders with PDO for example.</p>
<p>That&#8217;s the only solution worth recommending. Mentioning _escape() for the fivemillionandthwohundredthirtythousandandfiftysecond time OTH won&#8217;t do much good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 3 suggerimenti per lo sviluppo difensivo : phpblog.it</title>
		<link>http://www.brownphp.com/2008/12/three-important-tips-to-write-php-code-defensively/comment-page-1/#comment-493</link>
		<dc:creator>3 suggerimenti per lo sviluppo difensivo : phpblog.it</dc:creator>
		<pubDate>Tue, 30 Dec 2008 06:00:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownphp.com/?p=39#comment-493</guid>
		<description>[...] Douglas Brown propone dei semplici suggerimenti per scrivere codice difensivo facendo ricorso ad accorgimenti che sono dettati dalle best-practice ma che non sempre vengono messi in pratica specie quando si realizzano &#8220;cose facili&#8221; che magari &#8220;verranno usate solo per poco&#8220;&#8230;frasi già sentite vero?   Condividi : [...]</description>
		<content:encoded><![CDATA[<p>[...] Douglas Brown propone dei semplici suggerimenti per scrivere codice difensivo facendo ricorso ad accorgimenti che sono dettati dalle best-practice ma che non sempre vengono messi in pratica specie quando si realizzano &#8220;cose facili&#8221; che magari &#8220;verranno usate solo per poco&#8220;&#8230;frasi già sentite vero?   Condividi : [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vivanno.com::aggregator &#187; Archive &#187; Code défensif</title>
		<link>http://www.brownphp.com/2008/12/three-important-tips-to-write-php-code-defensively/comment-page-1/#comment-491</link>
		<dc:creator>vivanno.com::aggregator &#187; Archive &#187; Code défensif</dc:creator>
		<pubDate>Mon, 29 Dec 2008 22:22:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownphp.com/?p=39#comment-491</guid>
		<description>[...] &#160;Three Important Tips to Write PHP Code Defensively () [...]</description>
		<content:encoded><![CDATA[<p>[...] &nbsp;Three Important Tips to Write PHP Code Defensively () [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Douglas Brown&#8217;s Blog: Three Important Tips to Write PHP Code Defensively : Dragonfly Networks</title>
		<link>http://www.brownphp.com/2008/12/three-important-tips-to-write-php-code-defensively/comment-page-1/#comment-473</link>
		<dc:creator>Douglas Brown&#8217;s Blog: Three Important Tips to Write PHP Code Defensively : Dragonfly Networks</dc:creator>
		<pubDate>Fri, 26 Dec 2008 11:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownphp.com/?p=39#comment-473</guid>
		<description>[...] Brown has a few helpful hints to help you write your PHP code defensively, protecting your code from malicious [...]</description>
		<content:encoded><![CDATA[<p>[...] Brown has a few helpful hints to help you write your PHP code defensively, protecting your code from malicious [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Douglas Brown&#8217;s Blog: Three Important Tips to Write PHP Code Defensively : WebNetiques</title>
		<link>http://www.brownphp.com/2008/12/three-important-tips-to-write-php-code-defensively/comment-page-1/#comment-349</link>
		<dc:creator>Douglas Brown&#8217;s Blog: Three Important Tips to Write PHP Code Defensively : WebNetiques</dc:creator>
		<pubDate>Wed, 24 Dec 2008 10:18:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.brownphp.com/?p=39#comment-349</guid>
		<description>[...] Brown has a few helpful hints to help you write your PHP code defensively, protecting your code from malicious [...]</description>
		<content:encoded><![CDATA[<p>[...] Brown has a few helpful hints to help you write your PHP code defensively, protecting your code from malicious [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

