1995-02-03 - Re: Remailer Unreliability
Header Data
From: anonymous-remailer@shell.portal.com
To: cypherpunks@toad.com
Message Hash: 5839a3e9118e68d454d9d4ddb9f005b9d72476be9e0bf8014c8e982bea23c61e
Message ID: <199502030300.TAA10357@jobe.shell.portal.com>
Reply To: <m0raAVp-000vl1C@myriad.pc.cc.cmu.edu>
UTC Datetime: 1995-02-03 03:01:25 UTC
Raw Date: Thu, 2 Feb 95 19:01:25 PST
Raw message
From: anonymous-remailer@shell.portal.com
Date: Thu, 2 Feb 95 19:01:25 PST
To: cypherpunks@toad.com
Subject: Re: Remailer Unreliability
In-Reply-To: <m0raAVp-000vl1C@myriad.pc.cc.cmu.edu>
Message-ID: <199502030300.TAA10357@jobe.shell.portal.com>
MIME-Version: 1.0
Content-Type: text/plain
> Date: Thu, 2 Feb 95 18:00 EST
> From: nobody@myriad.pc.cc.cmu.edu (Anonymous)
>
> What if it was possible to specify an alternate remailer? In the case that
> a remailer went down, you could specify an alternate. For example:
Well, *I* think it is a good idea. But how does remailer1 know that
remailer2 is both a remailer and down?
Noyb
Thread
Return to February 1995
- Return to “anonymous-remailer@shell.portal.com”
- Return to “nobody@myriad.pc.cc.cmu.edu (Anonymous)”
Return to “Robert Rothenburg Walking-Owl <rrothenb@ic.sunysb.edu>”
- 1995-02-02 (Thu, 2 Feb 95 14:56:26 PST) - Remailer Unreliability - nobody@myriad.pc.cc.cmu.edu (Anonymous)
- 1995-02-03 (Thu, 2 Feb 95 18:36:54 PST) - Re: Remailer Unreliability - Robert Rothenburg Walking-Owl <rrothenb@ic.sunysb.edu>
- 1995-02-03 (Thu, 2 Feb 95 19:01:25 PST) - Re: Remailer Unreliability - anonymous-remailer@shell.portal.com