<?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: Follow-up to &#8220;A Hopefully Usefull Tutorial For Using CakePHP&#8217;s Auth Component&#8221;</title>
	<atom:link href="http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/</link>
	<description>Facebook should&#039;ve be written in unicornSchemaLang, because everyone *knows* that PHP is no good for anything, right?</description>
	<lastBuildDate>Mon, 09 Aug 2010 16:04:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Erik Gyepes</title>
		<link>http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/comment-page-1/#comment-10568</link>
		<dc:creator>Erik Gyepes</dc:creator>
		<pubDate>Mon, 30 Jun 2008 14:53:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/#comment-10568</guid>
		<description>I don&#039;t know what I&#039;m doing bad, but it doesn&#039;t work for me in Opera. When I reopen it my &quot;session&quot; is lost and I must relogin. In FF it works correctly.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know what I&#8217;m doing bad, but it doesn&#8217;t work for me in Opera. When I reopen it my &#8220;session&#8221; is lost and I must relogin. In FF it works correctly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: leo</title>
		<link>http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/comment-page-1/#comment-8637</link>
		<dc:creator>leo</dc:creator>
		<pubDate>Mon, 25 Feb 2008 14:56:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/#comment-8637</guid>
		<description>Thanks Chris. It&#039;s taken me days to get this working. Nowhere does it seem to clearly say that the stored password must be hashed, nor that the easiest way to do it is by using cake to insert the user. One of your articles has pointed me in the right direction once again!</description>
		<content:encoded><![CDATA[<p>Thanks Chris. It&#8217;s taken me days to get this working. Nowhere does it seem to clearly say that the stored password must be hashed, nor that the easiest way to do it is by using cake to insert the user. One of your articles has pointed me in the right direction once again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anh</title>
		<link>http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/comment-page-1/#comment-8634</link>
		<dc:creator>Anh</dc:creator>
		<pubDate>Sun, 24 Feb 2008 14:17:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/#comment-8634</guid>
		<description>Well, I think I figured that out. Just change the code in beforeFilter() to the following and it would work:

$cookie = $this-&gt;Cookie-&gt;read(&#039;User&#039;);
if ($cookie) {			
	$this-&gt;Auth-&gt;login($cookie);
}</description>
		<content:encoded><![CDATA[<p>Well, I think I figured that out. Just change the code in beforeFilter() to the following and it would work:</p>
<p>$cookie = $this-&gt;Cookie-&gt;read(&#8216;User&#8217;);<br />
if ($cookie) {<br />
	$this-&gt;Auth-&gt;login($cookie);<br />
}</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anh</title>
		<link>http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/comment-page-1/#comment-8633</link>
		<dc:creator>Anh</dc:creator>
		<pubDate>Sun, 24 Feb 2008 13:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/#comment-8633</guid>
		<description>I have some problems trying to implementing the Remember me feature. 

I followed your previous tutorial and store the username as well as the hashed password in the cookie. Then, in beforeFilter(), I put these values into the $this-&gt;data array. However, seems that the password in $this-&gt;data has to be plaintext, as the Auth component will automatically hash all passwords in this array. 

Did I miss anything?</description>
		<content:encoded><![CDATA[<p>I have some problems trying to implementing the Remember me feature. </p>
<p>I followed your previous tutorial and store the username as well as the hashed password in the cookie. Then, in beforeFilter(), I put these values into the $this-&gt;data array. However, seems that the password in $this-&gt;data has to be plaintext, as the Auth component will automatically hash all passwords in this array. </p>
<p>Did I miss anything?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Hartjes</title>
		<link>http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/comment-page-1/#comment-8424</link>
		<dc:creator>Chris Hartjes</dc:creator>
		<pubDate>Sat, 05 Jan 2008 15:47:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/#comment-8424</guid>
		<description>@Kabturek
Well, perhaps I don&#039;t understand how the hashing of the passwords works in the Auth component, but since the hash is only one way I don&#039;t see how anyone could even figure out the password unless they know the original.  I would be storing a *hashed* password in the cookie, not the plaintext one.  Storing plaintext passwords in a cookie is an insane security hole.</description>
		<content:encoded><![CDATA[<p>@Kabturek<br />
Well, perhaps I don&#8217;t understand how the hashing of the passwords works in the Auth component, but since the hash is only one way I don&#8217;t see how anyone could even figure out the password unless they know the original.  I would be storing a *hashed* password in the cookie, not the plaintext one.  Storing plaintext passwords in a cookie is an insane security hole.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kabturek</title>
		<link>http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/comment-page-1/#comment-8423</link>
		<dc:creator>kabturek</dc:creator>
		<pubDate>Sat, 05 Jan 2008 10:40:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/#comment-8423</guid>
		<description>@Chris
yep but i rather store an ID of the user (encrypted with a salt) if the cookie will be compromised i would only have to change the salt ( or the login system) and no paswords would be leaked.</description>
		<content:encoded><![CDATA[<p>@Chris<br />
yep but i rather store an ID of the user (encrypted with a salt) if the cookie will be compromised i would only have to change the salt ( or the login system) and no paswords would be leaked.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Hartjes</title>
		<link>http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/comment-page-1/#comment-8365</link>
		<dc:creator>Chris Hartjes</dc:creator>
		<pubDate>Thu, 20 Dec 2007 14:38:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/#comment-8365</guid>
		<description>@SFI: The purpose of storing the username and password in a cookie is so that when the user comes back to the site at a later date, they can be automatically logged in.</description>
		<content:encoded><![CDATA[<p>@SFI: The purpose of storing the username and password in a cookie is so that when the user comes back to the site at a later date, they can be automatically logged in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Hofstetter</title>
		<link>http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/comment-page-1/#comment-8364</link>
		<dc:creator>Daniel Hofstetter</dc:creator>
		<pubDate>Thu, 20 Dec 2007 05:56:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/#comment-8364</guid>
		<description>@Martin: Many people use the same password for different applications. So if I can get the password then it is possible I will also get access to other applications in a worst-case scenario.</description>
		<content:encoded><![CDATA[<p>@Martin: Many people use the same password for different applications. So if I can get the password then it is possible I will also get access to other applications in a worst-case scenario.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SFI</title>
		<link>http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/comment-page-1/#comment-8363</link>
		<dc:creator>SFI</dc:creator>
		<pubDate>Thu, 20 Dec 2007 04:13:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/#comment-8363</guid>
		<description>am I missing something..? I don&#039;t see the point of storing a username and password in a cookie... why not store using a session and have authenticated=true and if you want more security put the ip in so if someone hijacks the session cookie they can&#039;t use it ??</description>
		<content:encoded><![CDATA[<p>am I missing something..? I don&#8217;t see the point of storing a username and password in a cookie&#8230; why not store using a session and have authenticated=true and if you want more security put the ip in so if someone hijacks the session cookie they can&#8217;t use it ??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Schapendonk</title>
		<link>http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/comment-page-1/#comment-8361</link>
		<dc:creator>Martin Schapendonk</dc:creator>
		<pubDate>Wed, 19 Dec 2007 14:47:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.littlehart.net/atthekeyboard/2007/11/20/follow-up-to-a-hopefully-usefull-tutorial-for-using-cakephps-auth-component/#comment-8361</guid>
		<description>Daniel, Chris, others,

Nice to see how people try to prevent reverse engineering of a password from a cookie.

However, I miss one thing in the discussion... if I have the cookie, I don&#039;t *need* the password anymore! I just offer the cookie to the server and it logs me in. Who cares about the password?

BTW, I guess most (if not all) &#039;Remember Me&#039; solutions are vulnerable to &#039;cookie hijacking&#039;.</description>
		<content:encoded><![CDATA[<p>Daniel, Chris, others,</p>
<p>Nice to see how people try to prevent reverse engineering of a password from a cookie.</p>
<p>However, I miss one thing in the discussion&#8230; if I have the cookie, I don&#8217;t *need* the password anymore! I just offer the cookie to the server and it logs me in. Who cares about the password?</p>
<p>BTW, I guess most (if not all) &#8216;Remember Me&#8217; solutions are vulnerable to &#8216;cookie hijacking&#8217;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
