1994-04-10 - Re: REMAIL: pseudo-account remailer @andrew gains anonymous feature

Header Data

From: Matthew J Ghio <mg5n+@andrew.cmu.edu>
To: cypherpunks@toad.com
Message Hash: 6ebf9583fa1ce6e6732aa5b591a16e5942313e3b2562262ab7b0a4badc082705
Message ID: <Qhe4WQy00VpQ08oUgC@andrew.cmu.edu>
Reply To: <Pine.3.85.9404091920.A25730-0100000@netcom4>
UTC Datetime: 1994-04-10 18:44:14 UTC
Raw Date: Sun, 10 Apr 94 11:44:14 PDT

Raw message

From: Matthew J Ghio <mg5n+@andrew.cmu.edu>
Date: Sun, 10 Apr 94 11:44:14 PDT
To: cypherpunks@toad.com
Subject: Re: REMAIL: pseudo-account remailer @andrew gains anonymous feature
In-Reply-To: <Pine.3.85.9404091920.A25730-0100000@netcom4>
Message-ID: <Qhe4WQy00VpQ08oUgC@andrew.cmu.edu>
MIME-Version: 1.0
Content-Type: text/plain


Ed Carp <ecarp@netcom.com> wrote:

> How about generating a secure hash and using that as an index
> into a table?  If there's an address already there, use that -
> otherwise, generate one.
> 
> Generate the hash from the incoming address, of course.  That way,
> you  don't need to keep track of anon-id-to-real-id mappings, yet
> guarantee that each user has one and only one anon address. Of
> course, folks coming in from different hosts will have different
> anon ID's.
> 
> Or have I missed some blindingly obvious technical point thaqt
> would make this impossible?

I don't see how this would prevent me from having to keep track of
anon-id-to-real-id mappings.  It could work for sending mail, but I'd
still have to have some way of keeping track of the real ids for the
replies.





Thread