<?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: Computer souls</title>
	<atom:link href="http://dangerousintersection.org/2009/04/24/computer-souls/feed/" rel="self" type="application/rss+xml" />
	<link>http://dangerousintersection.org/2009/04/24/computer-souls/</link>
	<description>Human Animals at the Crossroads of Culture, Science, Religion and Media</description>
	<pubDate>Sun, 21 Mar 2010 07:32:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dan Klarmann</title>
		<link>http://dangerousintersection.org/2009/04/24/computer-souls/comment-page-1/#comment-39759</link>
		<dc:creator>Dan Klarmann</dc:creator>
		<pubDate>Tue, 19 May 2009 13:50:26 +0000</pubDate>
		<guid isPermaLink="false">http://dangerousintersection.org/?p=6440#comment-39759</guid>
		<description>Legacy Locker is a good idea. But I've used a local solution that costs less: I have an encrypted file with a strong password on my computer that contains all the critical information about accounts and passwords. The file name is obscure and its password is unguessable by social and dictionary means. I haven't tested the password with &lt;a href="http://en.wikipedia.org/wiki/L0phtCrack" target="_blank" rel="nofollow"&gt;L0phtCrack&lt;/a&gt;, but it follows the conventions).

Relevant heirs know about the file and the password, and that a copy of the file is in my safe deposit box at the bank (with a regular back up of my drive).

I figure that if my house burns down along with all my local back ups, the bank vault is safe. And cheaper than Legacy Locker.</description>
		<content:encoded><![CDATA[<p>Legacy Locker is a good idea. But I&#8217;ve used a local solution that costs less: I have an encrypted file with a strong password on my computer that contains all the critical information about accounts and passwords. The file name is obscure and its password is unguessable by social and dictionary means. I haven&#8217;t tested the password with <a href="http://en.wikipedia.org/wiki/L0phtCrack" target="_blank" rel="nofollow">L0phtCrack</a>, but it follows the conventions).</p>
<p>Relevant heirs know about the file and the password, and that a copy of the file is in my safe deposit box at the bank (with a regular back up of my drive).</p>
<p>I figure that if my house burns down along with all my local back ups, the bank vault is safe. And cheaper than Legacy Locker.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erich Vieth</title>
		<link>http://dangerousintersection.org/2009/04/24/computer-souls/comment-page-1/#comment-39748</link>
		<dc:creator>Erich Vieth</dc:creator>
		<pubDate>Tue, 19 May 2009 00:17:28 +0000</pubDate>
		<guid isPermaLink="false">http://dangerousintersection.org/?p=6440#comment-39748</guid>
		<description>What happens to your digital on-line life once you die?  Here's what:  http://www.cnn.com/2009/TECH/05/18/death.online/index.html?iref=t2test_techmon</description>
		<content:encoded><![CDATA[<p>What happens to your digital on-line life once you die?  Here&#8217;s what:  <a href="http://www.cnn.com/2009/TECH/05/18/death.online/index.html?iref=t2test_techmon" rel="nofollow">http://www.cnn.com/2009/TECH/05/18/death.online/index.html?iref=t2test_techmon</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
