<?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 for NickTelford.net</title>
	<atom:link href="http://nicktelford.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://nicktelford.net</link>
	<description>Software Development in an evolving world</description>
	<lastBuildDate>Thu, 12 Nov 2009 21:30:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Documenting Code Correctly by Roy Patterson</title>
		<link>http://nicktelford.net/2009/02/18/documenting-code-correctly/comment-page-1/#comment-8</link>
		<dc:creator>Roy Patterson</dc:creator>
		<pubDate>Thu, 12 Nov 2009 21:30:46 +0000</pubDate>
		<guid isPermaLink="false">http://lazesharp.net/?p=30#comment-8</guid>
		<description>I concur.</description>
		<content:encoded><![CDATA[<p>I concur.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Trust, Twitter and Passwords 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>Comment on Trust, Twitter and Passwords 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>
	<item>
		<title>Comment on Lies, deceit and Christians by Lazesharp.net &#187; Blog Archive &#187; How to fool the media</title>
		<link>http://nicktelford.net/2006/11/16/lies-deceit-and-christians/comment-page-1/#comment-1</link>
		<dc:creator>Lazesharp.net &#187; Blog Archive &#187; How to fool the media</dc:creator>
		<pubDate>Tue, 25 Dec 2007 15:31:38 +0000</pubDate>
		<guid isPermaLink="false">http://lazesharp.net/index.php/2006/11/16/lies-deceit-and-christians/#comment-1</guid>
		<description>[...] website here has opened my eyes to the ineptitude of journalists around the country, not only in researching the facts but also in attaining [...]</description>
		<content:encoded><![CDATA[<p>[...] website here has opened my eyes to the ineptitude of journalists around the country, not only in researching the facts but also in attaining [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A frontend for configuring FUSE filesystems by dimitri</title>
		<link>http://nicktelford.net/2007/06/19/frontend-for-configuring-fuse-filesystems/comment-page-1/#comment-3</link>
		<dc:creator>dimitri</dc:creator>
		<pubDate>Mon, 09 Jul 2007 08:09:54 +0000</pubDate>
		<guid isPermaLink="false">http://lazesharp.net/index.php/2007/06/19/a-frontend-for-fuse-based-filesystem-configuration/#comment-3</guid>
		<description>Hi, I was thinking about working on a similar tool -&gt; what is your status on this and is there chance of cooperation? For instance, I could help you with the GTK front-end, or anything else. Please reply by mail

Dimitri</description>
		<content:encoded><![CDATA[<p>Hi, I was thinking about working on a similar tool -&gt; what is your status on this and is there chance of cooperation? For instance, I could help you with the GTK front-end, or anything else. Please reply by mail</p>
<p>Dimitri</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A frontend for configuring FUSE filesystems by Alex Forrow</title>
		<link>http://nicktelford.net/2007/06/19/frontend-for-configuring-fuse-filesystems/comment-page-1/#comment-2</link>
		<dc:creator>Alex Forrow</dc:creator>
		<pubDate>Tue, 19 Jun 2007 23:06:30 +0000</pubDate>
		<guid isPermaLink="false">http://lazesharp.net/index.php/2007/06/19/a-frontend-for-fuse-based-filesystem-configuration/#comment-2</guid>
		<description>Sounds pretty dam good. It&#039;ll be good to have a good UI to get no-hassle filesystem access to remote hosts on a per-user basis. NFS is good(-ish) but is not much use if you don&#039;t have root (not to mention its routing complexities, and oh yeah, total lack of security). Few things to add though:

You say it should connect on start-up, but sometimes wouldn&#039;t it be better to connect as the user logs in? If a system had loads of users (on NIS or similar) it would be crazy to mount them all even when they may not be used. Also, on a laptop network connections may not be available until the user has logged in and connected to wireless. Maybe there could be an option for this?

Also, the use of authorized_keys is good, but that would allow any form of ssh use on the remote host with no authentication (which may or may not be acceptable). Would the gnome-keyring be useful here to store passwords?

Lastly, I think there&#039;s a typo where you mean fusetab instead of fstab :p

Good work with that, look forward to seeing something.

Alex</description>
		<content:encoded><![CDATA[<p>Sounds pretty dam good. It&#8217;ll be good to have a good UI to get no-hassle filesystem access to remote hosts on a per-user basis. NFS is good(-ish) but is not much use if you don&#8217;t have root (not to mention its routing complexities, and oh yeah, total lack of security). Few things to add though:</p>
<p>You say it should connect on start-up, but sometimes wouldn&#8217;t it be better to connect as the user logs in? If a system had loads of users (on NIS or similar) it would be crazy to mount them all even when they may not be used. Also, on a laptop network connections may not be available until the user has logged in and connected to wireless. Maybe there could be an option for this?</p>
<p>Also, the use of authorized_keys is good, but that would allow any form of ssh use on the remote host with no authentication (which may or may not be acceptable). Would the gnome-keyring be useful here to store passwords?</p>
<p>Lastly, I think there&#8217;s a typo where you mean fusetab instead of fstab :p</p>
<p>Good work with that, look forward to seeing something.</p>
<p>Alex</p>
]]></content:encoded>
	</item>
</channel>
</rss>
