<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Comments on snippet: 'Anti-SQL Injection Function'</title>
<link>http://snipplr.com</link>
<description>Snipplr comments feed'</description>
<language>en-us</language>
<pubDate>Tue, 14 Feb 2012 06:24:12 GMT</pubDate>
<item>
<title>fjckls said on 4/19/11</title>
<link>http://snipplr.com/view/2742/antisql-injection-function/</link>
<description><![CDATA[ what about this:
http://www.w3schools.com/PHP/func_mysql_real_escape_string.asp ]]></description>
<pubDate>Tue, 19 Apr 2011 23:18:12 GMT</pubDate>
<guid>http://snipplr.com/view/2742/antisql-injection-function/</guid>
</item>
<item>
<title>timkinnane said on 3/22/11</title>
<link>http://snipplr.com/view/2742/antisql-injection-function/</link>
<description><![CDATA[ append != prefix
append = suffix
prepend = prefix ]]></description>
<pubDate>Tue, 22 Mar 2011 18:02:19 GMT</pubDate>
<guid>http://snipplr.com/view/2742/antisql-injection-function/</guid>
</item>
<item>
<title>adkatrit said on 2/18/11</title>
<link>http://snipplr.com/view/2742/antisql-injection-function/</link>
<description><![CDATA[ This does not prevent sql injection.  It takes care of several special characters, and that's about it.   it does nothing to prevent the injection of wildcard characters such as % and _ also consider numerical values in sql terms, they do not need to be enclosed in single or double quotes, so mysql_real_escape_string, does just that.  It escapes strings.  Notice the function was not called mysql_prevent_injection.  This is why sql injection is still in the wild:  developers that are trying to find an easy solution to something that is implementation specific and requires attention to detail for mitigation.  If you want to prevent or lessen the risk of sql injection, read more about implementing sql injection not about preventing sql injection.  You'll find much more useful solutions by reading the blogs or books written by pentesters who are actively trying to defeat these protections.... just saying ]]></description>
<pubDate>Fri, 18 Feb 2011 05:17:51 GMT</pubDate>
<guid>http://snipplr.com/view/2742/antisql-injection-function/</guid>
</item>
<item>
<title>toltmanns said on 1/6/11</title>
<link>http://snipplr.com/view/2742/antisql-injection-function/</link>
<description><![CDATA[ sarfraznawaz2005 - what else can be done to secure the input to a further degree? ]]></description>
<pubDate>Thu, 06 Jan 2011 04:20:24 GMT</pubDate>
<guid>http://snipplr.com/view/2742/antisql-injection-function/</guid>
</item>
<item>
<title>sarfraznawaz2005 said on 2/11/09</title>
<link>http://snipplr.com/view/2742/antisql-injection-function/</link>
<description><![CDATA[ With mysql_real_escape_string alone, you are not 100% secure, consider going for function titled "Prevent SQL Injection". ]]></description>
<pubDate>Wed, 11 Feb 2009 00:38:26 GMT</pubDate>
<guid>http://snipplr.com/view/2742/antisql-injection-function/</guid>
</item>
<item>
<title>sarfraznawaz2005 said on 2/11/09</title>
<link>http://snipplr.com/view/2742/antisql-injection-function/</link>
<description><![CDATA[ With mysql_real_escape_string alone, you are not 100% secure, consider going for function titled "Prevent SQL Injection". ]]></description>
<pubDate>Wed, 11 Feb 2009 00:37:46 GMT</pubDate>
<guid>http://snipplr.com/view/2742/antisql-injection-function/</guid>
</item>
<item>
<title>llbbl said on 4/2/08</title>
<link>http://snipplr.com/view/2742/antisql-injection-function/</link>
<description><![CDATA[ <p>*append = prefix</p> ]]></description>
<pubDate>Wed, 02 Apr 2008 15:32:55 GMT</pubDate>
<guid>http://snipplr.com/view/2742/antisql-injection-function/</guid>
</item>
<item>
<title>llbbl said on 4/2/08</title>
<link>http://snipplr.com/view/2742/antisql-injection-function/</link>
<description><![CDATA[ <p>"mysqlrealescapestring() requires that a valid mysql connection"</p>

<p>The "mysql_" appended to the function might have been a clue. :)</p> ]]></description>
<pubDate>Wed, 02 Apr 2008 15:30:11 GMT</pubDate>
<guid>http://snipplr.com/view/2742/antisql-injection-function/</guid>
</item>
<item>
<title>philipolson said on 2/27/08</title>
<link>http://snipplr.com/view/2742/antisql-injection-function/</link>
<description><![CDATA[ <p>Note: mysql<em>real</em>escape<em>string() requires that a valid mysql connection (mysql</em>connect()) exists to work... see the PHP manual for details.</p> ]]></description>
<pubDate>Wed, 27 Feb 2008 17:04:05 GMT</pubDate>
<guid>http://snipplr.com/view/2742/antisql-injection-function/</guid>
</item>
<item>
<title>Shocker said on 1/30/08</title>
<link>http://snipplr.com/view/2742/antisql-injection-function/</link>
<description><![CDATA[ <p>Please note almost any string values used in mysql queries should be escaped and not all of these values is user input which has escaped characters from magic quotes GPC. (e.g. regular vars from the script)</p>

<p>I'd add an additional optional parameter (bool) which defines, whether the parameter $dirty is coming from a GPC variable or not. :)</p>
 ]]></description>
<pubDate>Wed, 30 Jan 2008 04:35:21 GMT</pubDate>
<guid>http://snipplr.com/view/2742/antisql-injection-function/</guid>
</item>
</channel>
</rss>
