1996-05-23 - (Another) alternative to remailer shutdowns

Header Data

From: Leonard Janke <janke@unixg.ubc.ca>
To: cypherpunks@toad.com
Message Hash: 5c10cb99155d6ef31c0fb4a63d4a72d8f5611602b7030fbbab4fb6a3c351fdde
Message ID: <Pine.SOL.3.91.960522114403.19500A-100000@netinfo.ubc.ca>
Reply To: N/A
UTC Datetime: 1996-05-23 04:14:54 UTC
Raw Date: Thu, 23 May 1996 12:14:54 +0800

Raw message

From: Leonard Janke <janke@unixg.ubc.ca>
Date: Thu, 23 May 1996 12:14:54 +0800
To: cypherpunks@toad.com
Subject: (Another) alternative to remailer shutdowns
Message-ID: <Pine.SOL.3.91.960522114403.19500A-100000@netinfo.ubc.ca>
MIME-Version: 1.0
Content-Type: text/plain



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