1996-05-23 - Re: Long-Lived Remailers

Header Data

From: Loren James Rittle <rittle@comm.mot.com>
To: dsmith@prairienet.org
Message Hash: 1bb8889781d61395c9e75b221025a66d1658b784ef9743ccacad6550c5410e64
Message ID: <9605230140.AA12217@supra.comm.mot.com>
Reply To: <199605212215.RAA13102@cdale1.midwest.net>
UTC Datetime: 1996-05-23 06:10:54 UTC
Raw Date: Thu, 23 May 1996 14:10:54 +0800

Raw message

From: Loren James Rittle <rittle@comm.mot.com>
Date: Thu, 23 May 1996 14:10:54 +0800
To: dsmith@prairienet.org
Subject: Re: Long-Lived Remailers
In-Reply-To: <199605212215.RAA13102@cdale1.midwest.net>
Message-ID: <9605230140.AA12217@supra.comm.mot.com>
MIME-Version: 1.0
Content-Type: text/plain



>From: "David E. Smith" <dsmith@midwest.net>
>Date: Tue, 21 May 1996 17:31:23 -0600

>Actually, there's an Idea.  Set up a single address; use added
>headers in the style of:
>
>::
>Remailers-To-Chain: 7
>Remailers-To-Avoid: remailer@nsa.gov
>Final-Destination: tcmay@got.net

David,

This will not work.  The original sender must pick the path himself,
if maximum encryption to hide the final destination is to be used.
The properly used cypherpunks-style remailer network provides that as
long as even one remailer in the chain is trustworthy, your secret is
safe.  Under your scheme, if the first remailer is untrustworthy,
everything is blown.  This is because unless the original sender
pick's the path (or at least the last hop explicitly), the final
destination and message must be available to each hop.

Loren





Thread