1996-05-23 - Re: (Another) alternative to

Header Data

From: “Jay Haines” <jay_haines@connaught-usa.com>
To: “Leonard Janke” <cypherpunks@toad.com>
Message Hash: b564dbcce7acf1f66fac4ded5210394b680c5b87a740f4e4eb330d87b5e3917e
Message ID: <n1379284116.57328@flu.connaught-usa.com>
Reply To: N/A
UTC Datetime: 1996-05-23 16:26:03 UTC
Raw Date: Fri, 24 May 1996 00:26:03 +0800

Raw message

From: "Jay Haines" <jay_haines@connaught-usa.com>
Date: Fri, 24 May 1996 00:26:03 +0800
To: "Leonard Janke" <cypherpunks@toad.com>
Subject: Re: (Another) alternative to
Message-ID: <n1379284116.57328@flu.connaught-usa.com>
MIME-Version: 1.0
Content-Type: text/plain


        Reply to:   RE>(Another) alternative to remailer shutdowns

Where would these message parts be put back together/decrypted? Wouldn't this
require the receivers mail program to re-generate the original message?

--------------------------------------
Instead of having the last remailer in the chain store the plaintext of
an encrypted anonymous message, it might be more convenient to have the 
sender split the message into two messages and send these. The first 
message would contain random characters,  and the second would contain 
the xor of these random characters with the anonymous message. By themselves, 
each piece would, of course, be harmless random text, so remailer operators
greatest crime would be spamming. If the two pieces were sent through 
chains with different last remailers, no one operator could be held
accountable, and, of course, it would be ridiculous to suggest that
one operator could be held responsible for that fact that another
sent some random text which happened to be the xor of the random text
another had sent with a harassing message. (For instance, the
other operator could be trying to frame the first, with the
help of the receiver.) It seems to me that the only way to deal with a 
remailing scheme of this kind would be outlaw anonymous remalining in 
general.

Leonard







Thread