<?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: Injection Prevention &#8211; looping mysql_real_escape_string()</title>
	<atom:link href="http://createmy.com.au/injection-prevention-looping-mysql_real_escape_string/feed/" rel="self" type="application/rss+xml" />
	<link>http://createmy.com.au/injection-prevention-looping-mysql_real_escape_string/</link>
	<description>Create My - eCommerce - Web Development - Web Design - Dale Hurley</description>
	<lastBuildDate>Wed, 18 Apr 2012 03:23:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	

<!-- Debugging help, do not remove -->
<meta name="Framework" content="Kpress" />
<meta name="Theme Version" content="1.3" />
<meta name="Framework Version" content="1.3" />


	<item>
		<title>By: PHP Password Salt and Pepper using sha1 MD5 Hash &#124; Create My - eCommerce and Web Design Hornsby - eCommerces and Web Design Sydney</title>
		<link>http://createmy.com.au/injection-prevention-looping-mysql_real_escape_string/comment-page-1/#comment-91</link>
		<dc:creator>PHP Password Salt and Pepper using sha1 MD5 Hash &#124; Create My - eCommerce and Web Design Hornsby - eCommerces and Web Design Sydney</dc:creator>
		<pubDate>Thu, 15 Oct 2009 14:46:37 +0000</pubDate>
		<guid isPermaLink="false">http://createmy.com.au/?p=249#comment-91</guid>
		<description>[...] The Create My solution was to make it just that little bit more annoying and complicated to reverse adding enough deterrents for the hackers just find the time to break the encoding just too annoying. Along with encoding the password in the database you need to add SQL injection protection measures. [...]</description>
		<content:encoded><![CDATA[<p>[...] The Create My solution was to make it just that little bit more annoying and complicated to reverse adding enough deterrents for the hackers just find the time to break the encoding just too annoying. Along with encoding the password in the database you need to add SQL injection protection measures. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

