<?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"
	>
<channel>
	<title>Comments on: Storing passwords securely</title>
	<atom:link href="http://www.thespanner.co.uk/2007/02/06/storing-passwords-securely/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thespanner.co.uk/2007/02/06/storing-passwords-securely/</link>
	<description>A tool for designers dealing with programmers dealing with designers...</description>
	<pubDate>Fri, 10 Sep 2010 14:51:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Gareth Heyes</title>
		<link>http://www.thespanner.co.uk/2007/02/06/storing-passwords-securely/#comment-1365</link>
		<dc:creator>Gareth Heyes</dc:creator>
		<pubDate>Tue, 25 Nov 2008 11:29:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.thespanner.co.uk/?p=16#comment-1365</guid>
		<description>@alex

If they could read your php code then you have bigger problems but you could store the seed in a apache config variable or maybe use a unique seed per user within the table.</description>
		<content:encoded><![CDATA[<p>@alex</p>
<p>If they could read your php code then you have bigger problems but you could store the seed in a apache config variable or maybe use a unique seed per user within the table.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://www.thespanner.co.uk/2007/02/06/storing-passwords-securely/#comment-1364</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Mon, 24 Nov 2008 23:12:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.thespanner.co.uk/?p=16#comment-1364</guid>
		<description>How would you prevent someone from attacking your php code directly. If someone could read what your $seed is, they could do a reverse md5 and find out the password, then login</description>
		<content:encoded><![CDATA[<p>How would you prevent someone from attacking your php code directly. If someone could read what your $seed is, they could do a reverse md5 and find out the password, then login</p>
]]></content:encoded>
	</item>
</channel>
</rss>
