1993-03-29 - anonymous services

Header Data

From: Eric Hughes <hughes@soda.berkeley.edu>
To: cypherpunks@toad.com
Message Hash: e43945f403d79207f28a1f4b0c6a03b3c627a6a8f980c0af3bb2424e60578b73
Message ID: <9303291717.AA20805@soda.berkeley.edu>
Reply To: <9303290242.AA09702@toad.com>
UTC Datetime: 1993-03-29 14:36:45 UTC
Raw Date: Mon, 29 Mar 93 06:36:45 PST

Raw message

From: Eric Hughes <hughes@soda.berkeley.edu>
Date: Mon, 29 Mar 93 06:36:45 PST
To: cypherpunks@toad.com
Subject: anonymous services
In-Reply-To: <9303290242.AA09702@toad.com>
Message-ID: <9303291717.AA20805@soda.berkeley.edu>
MIME-Version: 1.0
Content-Type: text/plain

>A service which can be used as easily as anon.penet.fi would certainly be 

Right now the cypherpunks remailers are designed as a back end.
Clever people can program the back end directly, but it's not for

It's the user's software that should provide a good front end.  

>I'd also like to see encryption available as an option. Ideally, 
>messages would not _have_ to be encrypted. 

That's the way the current remailers work (with the exception of Miron
Cuperman's).  But fundamentally, there's no good reason not to
encrypt, except, of course, for the last hop out of a Usenet post.
The user's front end software should encrypt automatically.

Remember, you need to encrypt everything, so that when you really need
the protection, it doesn't appear as though anything is different.

>This would also accomodate people within the U.S. who want to use the 
>service put are afraid of Mr. Sternlight. :-)

The remailers could just as easily be built on top of RSAREF.
Licensing is a red herring for this project.