1993-01-12 - Cascading aliases with ID forwarding re-mailers
Header Data
From: hugh@domingo.teracons.com (Hugh Daniel)
To: cypherpunks@toad.com
Message Hash: 6f9bce1bf94389c121a8d54a42b9d81a07be3056423d207470915b4bb93214dc
Message ID: <9301122237.AA03911@domingo.teracons.com>
Reply To: <930109232813_74076.1041_DHJ76-1@CompuServe.COM>
UTC Datetime: 1993-01-12 22:39:03 UTC
Raw Date: Tue, 12 Jan 93 14:39:03 PST
Raw message
From: hugh@domingo.teracons.com (Hugh Daniel)
Date: Tue, 12 Jan 93 14:39:03 PST
To: cypherpunks@toad.com
Subject: Cascading aliases with ID forwarding re-mailers
In-Reply-To: <930109232813_74076.1041_DHJ76-1@CompuServe.COM>
Message-ID: <9301122237.AA03911@domingo.teracons.com>
MIME-Version: 1.0
Content-Type: text/plain
I suspect that a ID creating forwarder should _never_ send the ID to
the user, as someone might be looking (both the current plain text
replys and traffic analsys are problems). If the user wishes to know
their ID then they can send a message to themselvs, and read the ID
off of that, right?
||ugh Daniel
Thread
Return to January 1993
- Return to “Hal <74076.1041@CompuServe.COM>”
- Return to “hugh@domingo.teracons.com (Hugh Daniel)”
Return to “Johan Helsingius <julf@penet.FI>”
- 1993-01-09 (Sat, 9 Jan 93 15:33:30 PST) - Cascading aliases - Hal <74076.1041@CompuServe.COM>
- 1993-01-10 (Sun, 10 Jan 93 00:45:29 PST) - Re: Cascading aliases - Johan Helsingius <julf@penet.FI>
- 1993-01-12 (Tue, 12 Jan 93 14:39:03 PST) - Cascading aliases with ID forwarding re-mailers - hugh@domingo.teracons.com (Hugh Daniel)