1996-09-29 - Re: Making Remailers Widespread

Header Data

From: snow <snow@smoke.suba.com>
To: dlv@bwalk.dm.com (Dr.Dimitri Vulis KOTM)
Message Hash: 295fe3eab7fb8aae868b4ee7c26ed8417084f0190adacf4b0c529606cf7bf31c
Message ID: <199609290222.VAA00392@smoke.suba.com>
Reply To: <siyyuD50w165w@bwalk.dm.com>
UTC Datetime: 1996-09-29 05:01:01 UTC
Raw Date: Sun, 29 Sep 1996 13:01:01 +0800

Raw message

From: snow <snow@smoke.suba.com>
Date: Sun, 29 Sep 1996 13:01:01 +0800
To: dlv@bwalk.dm.com (Dr.Dimitri Vulis KOTM)
Subject: Re: Making Remailers Widespread
In-Reply-To: <siyyuD50w165w@bwalk.dm.com>
Message-ID: <199609290222.VAA00392@smoke.suba.com>
MIME-Version: 1.0
Content-Type: text


KOTM said:
> Bill Stewart <stewarts@ix.netcom.com> writes:
> > Doing two-way remailers would be better, but that's still a hard problem,
> > and I don't want to widely deploy shoddy two-way-remailers.

     While IANAC, maybe a suggestion here (and there might be holes in 
this) when the email is sent to the remailer, it gets a key pair generated,
and one of the keys is inserted into the header of the forwarded email
like this:

*****This is an anonymous message forwared from the spread remailer*****
*****To reply to this message, send email with the following 4 lines**** 
*****as the first part of the message to:                          *****

=>replykey:<key goes here.

     The reply address is encrypted with the other part of the key. It 
isn't real secure, but the server admin can't get the return addresses
without the key. 
    
     Off the top of my head, the biggest problem is that you can't send 
email to a web site (page).

     The other problem is that it would greatly add to the complexity
of the .pl program, and make it take much more overhead. What about
making the one way a .pl script, and the two way a module?       

    
Petro, Christopher C.
petro@suba.com <prefered for any non-list stuff>
snow@smoke.suba.com





Thread