1995-07-25 - Re: An idea about Java and remailer clients and servers…

Header Data

From: cman@communities.com (Douglas Barnes)
To: Ray Cromwell <rjc@clark.net>
Message Hash: f1853dd85f558301f642e9af10afd0714985237d8512848d9737d25c298c7b88
Message ID: <v02120d03ac39fe80b194@[199.2.22.120]>
Reply To: N/A
UTC Datetime: 1995-07-25 00:55:50 UTC
Raw Date: Mon, 24 Jul 95 17:55:50 PDT

Raw message

From: cman@communities.com (Douglas Barnes)
Date: Mon, 24 Jul 95 17:55:50 PDT
To: Ray Cromwell <rjc@clark.net>
Subject: Re: An idea about Java and remailer clients and servers...
Message-ID: <v02120d03ac39fe80b194@[199.2.22.120]>
MIME-Version: 1.0
Content-Type: text/plain



> I forgot to add. There is no reason User X has to run his remailer
>immediately. His software could simply commit to running a remailer for
>1 hour at some specified future date < some threshold. Any messages
>sent to him for remailing would be queued until that time. Therefore,
>all your technique would tell you is that the user remailed a message
>sometime between date X and date Y. if Y-X > few days to week or two,
>the intelligence gathered on User X is miniscule. Traffic analysis would
>detect User X using the remailer network anyway.
>

When I've thought about this, it's been from the p.o.v. of message
senders being able to earn prepaid service tokens (not unlike
digital cash) for offering their machine as a remailer for a set
period of time or number of message or total bandwidth or
whatever. This activity could be completely asynchronous to any
origination of messages, and, in fact, a regular habit of accumulating
tokens like this would make for excellent cover traffic.







Thread