<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://ideas.4brad.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Brad Ideas - &amp;quot;Better hope nothing happens to me&amp;quot; service. - Comments</title>
 <link>http://ideas.4brad.com/node/400</link>
 <description>Comments for &quot;&quot;Better hope nothing happens to me&quot; service.&quot;</description>
 <language>en</language>
<item>
 <title>The money flow is hard</title>
 <link>http://ideas.4brad.com/node/400#comment-1668</link>
 <description>&lt;p&gt;Unless you truly can pay cash, it&#039;s hard to hide the money flow.&lt;/p&gt;
&lt;p&gt;Plus, you may want a system which does not reveal the data when you truly die naturally.   In that case, you might be able to disable it as you see yourself getting old, but it&#039;s better if other humans verify things.   You would want to add emailing the press or other interested parties, but that&#039;s not hard.&lt;/p&gt;
&lt;p&gt;However, another problem is the web hosting company has the real data, and you don&#039;t want anybody to have it until you release it.  That&#039;s why you need a divided key.  You could have several web hosts and divide the key up among them, and have them send it on d-day to the host that has the encrypted data.&lt;/p&gt;
&lt;p&gt;However, there is a lot to be said for plans that use existing infrastructure.  However, with most of those plans, you can&#039;t demonstrate that you really did hide the data in a place it will get revealed, which is your best insurance policy.   Ideally you want them to be sure you really did it, but not able to get at it, and for the holders not to be able to read it.&lt;/p&gt;
</description>
 <pubDate>Sun, 07 May 2006 17:23:57 -0700</pubDate>
 <dc:creator>brad</dc:creator>
 <guid isPermaLink="false">comment 1668 at http://ideas.4brad.com</guid>
</item>
<item>
 <title>Unless I&#039;m misunderstanding</title>
 <link>http://ideas.4brad.com/node/400#comment-1667</link>
 <description>&lt;p&gt;Unless I&#039;m misunderstanding your challenge, this doesn&#039;t sound too hard to do. If your evidence can go onto the &#039;net, then all you need to do is set up a website that will take a page live on date/time X unless you log into the admin page and manually change the go-live date. IIRC, MovableType already has that kind of functionality out of the box, and even if they don&#039;t, it&#039;s a pretty trivial hack.&lt;/p&gt;
&lt;p&gt;All you&#039;d need is to set up and pay for a hosted website that isn&#039;t obviously tied to you. A bit more of a challenge, but if you could find a place that will allow you to pay cash for one of those preloaded Visa debit cards, then you could pay for the account without your actual name being attached it.&lt;/p&gt;
&lt;p&gt;You&#039;re still vulnerable to being tortured into revealing the location/password, though.&lt;/p&gt;
</description>
 <pubDate>Sun, 07 May 2006 15:11:57 -0700</pubDate>
 <dc:creator>lux</dc:creator>
 <guid isPermaLink="false">comment 1667 at http://ideas.4brad.com</guid>
</item>
<item>
 <title>Payment not enough</title>
 <link>http://ideas.4brad.com/node/400#comment-1652</link>
 <description>&lt;p&gt;Remember, unlike the traditional movie version, where the information is hidden in an unknown place, this modern computerized version actually provides proof that you have hidden the information to be revealed if you die.  So unless the service confirms it is you when you pay, the bad guys could just pay for you.&lt;/p&gt;
</description>
 <pubDate>Fri, 05 May 2006 01:38:52 -0700</pubDate>
 <dc:creator>brad</dc:creator>
 <guid isPermaLink="false">comment 1652 at http://ideas.4brad.com</guid>
</item>
<item>
 <title>Why not make the regular</title>
 <link>http://ideas.4brad.com/node/400#comment-1641</link>
 <description>&lt;p&gt;Why not make the regular payment as the notification that I&#039;m still alive? If the escrow does not get the payment then the service is terminated and the information made public.&lt;/p&gt;
</description>
 <pubDate>Wed, 03 May 2006 07:23:01 -0700</pubDate>
 <dc:creator>Jnsaff</dc:creator>
 <guid isPermaLink="false">comment 1641 at http://ideas.4brad.com</guid>
</item>
<item>
 <title>&quot;Better hope nothing happens to me&quot; service.</title>
 <link>http://ideas.4brad.com/node/400</link>
 <description>&lt;p&gt;Here&amp;#8217;s an interesting problem.   In the movies we always see scenes where the good guy is fighting the Evil Conspiracy (EvilCon) and he tells them he&amp;#8217;s hidden the incriminating evidence with a friend who will release it to the papers if the good guy disappears under mysterious circumstances.   Today EvilCon would just quickly mine your social networking platform to find all your friends and shake them down for the evidence.&lt;/p&gt;

&lt;p&gt;So here&amp;#8217;s the challenge.  Design a system so that if you want to escrow some evidence, you can do it quickly, reliably and not too expensively, at a brief stop at an internet terminal while on the run from EvilCon.   Assume EvilCon is extremely powerful, like the NSA.   Here are some of the challenges:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You need to be able to pay those who do escrow, as this is risky work.  At the same time there must be no way to trace the payment.&lt;/li&gt;
&lt;li&gt;You don&amp;#8217;t want the escrow agents to be able to read the data.  Instead, you will split the encryption keys among several escrow agents in a way that some subset of them must declare you missing to assemble the key and publish the data.&lt;/li&gt;
&lt;li&gt;You need some way to vet escrow agents to assure they will do their job faithfully, but at the same time you must assume some of them work for EvilCon if there is a large pool.&lt;/li&gt;
&lt;li&gt;They must have some way to check if you are still alive.  Regularly searching for you in Google or going to your web site regularly might be traced.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Some thoughts below&amp;#8230;&lt;/p&gt;
</description>
 <comments>http://ideas.4brad.com/node/400#comments</comments>
 <category domain="http://ideas.4brad.com/archives/cat_privacy.html">Privacy</category>
 <category domain="http://ideas.4brad.com/taxonomy/term/36">Solve this</category>
 <pubDate>Tue, 02 May 2006 00:03:15 -0700</pubDate>
 <dc:creator>brad</dc:creator>
 <guid isPermaLink="false">400 at http://ideas.4brad.com</guid>
</item>
</channel>
</rss>
