From: hughes@ah.com (Eric Hughes)
To: cypherpunks@toad.com
Message Hash: ec88ae4fb071f8b28e8d09b0ded2b6ae33aa0390defe26efb6d7852fb71278b1
Message ID: <9407271635.AA07788@ah.com>
Reply To: <Pine.3.87.9407270710.A25102-0100000@crl.crl.com>
UTC Datetime: 1994-07-27 16:57:05 UTC
Raw Date: Wed, 27 Jul 94 09:57:05 PDT
From: hughes@ah.com (Eric Hughes)
Date: Wed, 27 Jul 94 09:57:05 PDT
To: cypherpunks@toad.com
Subject: LITTLE BROTHER INSIDE
In-Reply-To: <Pine.3.87.9407270710.A25102-0100000@crl.crl.com>
Message-ID: <9407271635.AA07788@ah.com>
MIME-Version: 1.0
Content-Type: text/plain
Prior to seizure/theft, you would make an
arrangement with an offshore "escrow agent." After seizure you would
send your computer the instruction that says, "encrypt my disk with the
escrow agents public key."
You don't even need public key. Just place a secret key in the hands
of your if-duress-no-release agent and put the same key in the right
place in nonvolatile, but erasable, storage inside the computer. In a
standard PC, there's room for this in the battery-backed configuration
RAM, which has lots of extra space on many newer models.
The use of public key would still require that a session key for a
(fast) symmetric cipher be generated and then destroyed, so you're not
that much better off. The advantage is that you don't have to destroy
the public key. Since destruction is pretty easy for information, I
don't consider it much of an advantage.
And, lastly, if you were to use public key, you'd want the agent to
generate a key pair for your use only. This avoids linkage with other
information.
Eric
Return to July 1994
Return to “Yarkumila <yusuf921@raven.csrv.uidaho.edu>”