<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: PHP Security - Login using Challenge/Response Pattern for MVC</title>
	<link>http://www.melbournechapter.net/wordpress/programming-languages/php/cman/2006/03/14/php-security-login-using-challengeresponse-pattern-for-mvc/</link>
	<description>web application development with popular technologies</description>
	<pubDate>Tue, 02 Dec 2008 08:20:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: melbourne chapter &#187; PHP and Authentication Security</title>
		<link>http://www.melbournechapter.net/wordpress/programming-languages/php/cman/2006/03/14/php-security-login-using-challengeresponse-pattern-for-mvc/#comment-37</link>
		<pubDate>Mon, 03 Apr 2006 23:13:57 +0000</pubDate>
		<guid>http://www.melbournechapter.net/wordpress/programming-languages/php/cman/2006/03/14/php-security-login-using-challengeresponse-pattern-for-mvc/#comment-37</guid>
					<description>[...] A little while back I discussed the theory to how you can setup a Challenge/Response architecture using PHP and MVC pattern. This discussed ways of having the password hashed client side using a server issued &#8220;challenge&#8221; key to make a &#8220;response&#8221;. This allowed us to protect the password in clear text from being intercepted across a HTTP network. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] A little while back I discussed the theory to how you can setup a Challenge/Response architecture using PHP and MVC pattern. This discussed ways of having the password hashed client side using a server issued &#8220;challenge&#8221; key to make a &#8220;response&#8221;. This allowed us to protect the password in clear text from being intercepted across a HTTP network. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
