<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Trust, Twitter and Passwords</title>
	<atom:link href="http://nicktelford.net/2009/02/11/trust-twitter-and-passwords/feed/" rel="self" type="application/rss+xml" />
	<link>http://nicktelford.net/2009/02/11/trust-twitter-and-passwords/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Mon, 21 Jun 2010 22:09:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nicholas Telford</title>
		<link>http://nicktelford.net/2009/02/11/trust-twitter-and-passwords/comment-page-1/#comment-5</link>
		<dc:creator>Nicholas Telford</dc:creator>
		<pubDate>Wed, 11 Feb 2009 21:55:46 +0000</pubDate>
		<guid isPermaLink="false">http://lazesharp.net/?p=29#comment-5</guid>
		<description>The FriendFeed system is much more secure than the plain text system, granted. However it does have the draw back that the user has to explicitly discover their &quot;Remote Key&quot;. This is a concept that only really power users will easily grasp and overcomplicates the process.

I prefer the LiveJournal method because you ask the user for the password once (on an SSL domain) then you get a challenge from LiveJournal. You then sign every API call with a hash of the challenge and password. The great thing about this approach is that you can easily store this hash without the worry of the password being retrievable.</description>
		<content:encoded><![CDATA[<p>The FriendFeed system is much more secure than the plain text system, granted. However it does have the draw back that the user has to explicitly discover their &#8220;Remote Key&#8221;. This is a concept that only really power users will easily grasp and overcomplicates the process.</p>
<p>I prefer the LiveJournal method because you ask the user for the password once (on an SSL domain) then you get a challenge from LiveJournal. You then sign every API call with a hash of the challenge and password. The great thing about this approach is that you can easily store this hash without the worry of the password being retrievable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://nicktelford.net/2009/02/11/trust-twitter-and-passwords/comment-page-1/#comment-4</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Wed, 11 Feb 2009 21:39:02 +0000</pubDate>
		<guid isPermaLink="false">http://lazesharp.net/?p=29#comment-4</guid>
		<description>Surely a simpler solution would just be to incorporate an API Key system whereby each user get&#039;s allocated a random string, their key. Both friendfeed and wordpress incorporate this method.</description>
		<content:encoded><![CDATA[<p>Surely a simpler solution would just be to incorporate an API Key system whereby each user get&#8217;s allocated a random string, their key. Both friendfeed and wordpress incorporate this method.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
