1996-10-15 - [Repost] PipeNet

Header Data

From: Lucky Green <shamrock@netcom.com>
To: cypherpunks@toad.com
Message Hash: 979c221cc4f13d49fd65fb0780d973d64999e3f1b4337503665df6eae1d894fd
Message ID: <Pine.3.89.9610142215.A10086-0100000@netcom14>
Reply To: N/A
UTC Datetime: 1996-10-15 05:59:51 UTC
Raw Date: Mon, 14 Oct 1996 22:59:51 -0700 (PDT)

Raw message

From: Lucky Green <shamrock@netcom.com>
Date: Mon, 14 Oct 1996 22:59:51 -0700 (PDT)
To: cypherpunks@toad.com
Subject: [Repost] PipeNet
Message-ID: <Pine.3.89.9610142215.A10086-0100000@netcom14>
MIME-Version: 1.0
Content-Type: text/plain


Below is a repost of the original PipeNet article from February, 1995. 
The author is Wei Dai.

-----BEGIN PGP SIGNED MESSAGE-----

A week ago I made a suggestion for a new protocol for untracibility,
but only got one response.  I'll try again, this time more
forcefully.  I'm not trying to convince anyone to implement this
(though of course you're welcome to!), but just to think about it and
give me feedback.

Why is another protocol needed?  Right now we have only two,
each of which has its own set of tradeoffs.  To summarize:

        Mix-Net (i.e., remailer-net): high latency, moderate bandwidth
                costs, and low complexity
        DC-Net: moderate latency, high bandwidth costs, and high complexity

While the DC-Net will probably never be widely used, the remailer-net
has a fair chance of one day
providing a way for many people to send e-mail that not even governments
can trace.  However, I don't think this is enough.  Efficient
social and business relationships require that people be able to
converse to each other in real time.  Cryptoanarchy will not come about
if people cannot do this anonymously.  How well can two pseudonymous
agents negotiate a contract if each message they send must be delayed
several hours?  The protocol I sugguested would have low latency, moderate
bandwidth costs, and moderate complexity.  It would be well suited for
people to interact anonymously in a textual environment.

This is what I wrote:
> Imagine a server that allows you to open a
> low bandwidth (let's say around 100 cps, in order to reduce costs)
> link-encrypted telnet session with it, and provides you with a number
> of services, for example a link-encrypted talk session with another
> user.  You'll need to maintain the link 24 hours a day to defend
> against statistical analysis, and of course you can chain a number of
> these servers together in a way similiar to chaining remailers.

Lance pointed out the chain cannot be built quickly.  This is not a problem
if servers connect to each other with relatively wide link-encrypted pipes
and multiplex your connection into these pipes.

In this system, latency would never be more than a few seconds, bandwidth
cost is N*100 cps (point to point), N being the number of links in your 
chain.
Implementation would probably be harder than remailers, but much easier
than DC-Nets.  The protocol would also provide both sender and receiver
untracibility without any need for broadcasting.

Wei Dai

P.S. I never gave a name for the protocol... let's call it Pipe-net.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBLzgewDl0sXKgdnV5AQGzvAQAgFaOxOzFPgS031z4jZRYUJp/+3BS5Con
Kza7WsvZPvxzaNLh9ecD3aCx5dtf4muaiUKjC2HIItaLKEdZZPdzUGFd4wg1cY8G
k8mvYNzDImr3ZtQ0HiqQ59PWhznad0GuhjQajB7RtpI+K/Z4uBaUEZGVoZZT+LHN
MSjOl/k/yfg=
=jgq6
-----END PGP SIGNATURE-----








Thread