From: Ed Carp <ecarp@netcom.com>
To: Matthew J Ghio <mg5n+@andrew.cmu.edu>
Message Hash: 1056a0d77e3eb7d3335bee865f63c5c3cc43b1f9401275d3903ba7e0338ec43a
Message ID: <Pine.3.85.9404101329.A6126-0100000@netcom4>
Reply To: <Qhe4WQy00VpQ08oUgC@andrew.cmu.edu>
UTC Datetime: 1994-04-10 20:33:22 UTC
Raw Date: Sun, 10 Apr 94 13:33:22 PDT
From: Ed Carp <ecarp@netcom.com>
Date: Sun, 10 Apr 94 13:33:22 PDT
To: Matthew J Ghio <mg5n+@andrew.cmu.edu>
Subject: Re: REMAIL: pseudo-account remailer @andrew gains anonymous feature
In-Reply-To: <Qhe4WQy00VpQ08oUgC@andrew.cmu.edu>
Message-ID: <Pine.3.85.9404101329.A6126-0100000@netcom4>
MIME-Version: 1.0
Content-Type: text/plain
On Sun, 10 Apr 1994, Matthew J Ghio wrote:
> 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.
Ah, yes, I *knew* I had missed something obvious... Thanks.
Return to April 1994
Return to “ub075@freenet.victoria.bc.ca (Ryan A. Perkins)”