1998-01-18 - Re: how to release code if the programmer is a target for (fwd)

Header Data

From: Steve Schear <schear@lvdi.net>
To: Jim Choate <cypherpunks@ssz.com (Cypherpunks Distributed Remailer)
Message Hash: 4f026c2f82c4e8fb5d1e29f4a00adc8e1e704f5b946fe5605c52207acd481251
Message ID: <v03102808b0e809baaf1d@[208.129.55.202]>
Reply To: <199801180123.TAA16226@einstein.ssz.com>
UTC Datetime: 1998-01-18 19:49:21 UTC
Raw Date: Mon, 19 Jan 1998 03:49:21 +0800

Raw message

From: Steve Schear <schear@lvdi.net>
Date: Mon, 19 Jan 1998 03:49:21 +0800
To: Jim Choate <cypherpunks@ssz.com (Cypherpunks Distributed Remailer)
Subject: Re: how to release code if the programmer is a target for (fwd)
In-Reply-To: <199801180123.TAA16226@einstein.ssz.com>
Message-ID: <v03102808b0e809baaf1d@[208.129.55.202]>
MIME-Version: 1.0
Content-Type: text/plain



At 7:23 PM -0600 1/17/98, Jim Choate wrote:
>Forwarded message:
>
>> Subject: Re: how to release code if the programmer is a target for (fwd)
>> From: Ryan Lackey <rdl@mit.edu>
>> Date: 17 Jan 1998 19:07:10 -0500
>
>> Eternity delivers data.  It's up to the user to verify that the data is
>> what they want
>
>> The original question was how to verify the eternity server source code.
>
>How are these fundamently different? Assume for a moment that as a user of
>an eternity server the source is the data I want.

(I didn't see anyone comment on my posting under "Re: remailer resistancs to attack", so I thought I'd repost under this thread.  My apologies for any inconvience.)

Came across this paper and thought it might contribute to improving remailer reliability, "How to Maintain Authenticated Communication in the Presence of Break-ins," http://theory.lcs.mit.edu/~tcryptol/OLD/old-02.html

--Steve







Thread