1993-09-17 - Re: Remail: errors

Header Data

From: rjc@gnu.ai.mit.edu (Ray)
To: HFinney@shell.portal.com
Message Hash: 45290ecd77167cca476d0de5915f1f116113693a37704614fbd7732fd53f04f4
Message ID: <9309170610.AA29796@geech.gnu.ai.mit.edu>
Reply To: <9309150646.AA29585@jobe.shell.portal.com>
UTC Datetime: 1993-09-17 06:14:54 UTC
Raw Date: Thu, 16 Sep 93 23:14:54 PDT

Raw message

From: rjc@gnu.ai.mit.edu (Ray)
Date: Thu, 16 Sep 93 23:14:54 PDT
To: HFinney@shell.portal.com
Subject: Re: Remail: errors
In-Reply-To: <9309150646.AA29585@jobe.shell.portal.com>
Message-ID: <9309170610.AA29796@geech.gnu.ai.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain


HFinney@shell.portal.com () writes:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> 
> I have been out of town for the last week, so I missed some CP mail.
> It looks like some good things are happening with remailers, though.
> Kudos to Karl, Sameer, and the others for their work!
> 
> I have received many messages to my remailer in the last week which
> came from remail@tamsun.tamu.edu, which were PGP-encrypted apparently
> in an effort to get my remailer to send them.
> 
> They did not work, though, because there was no "Encrypted: PGP" header
> to trigger the remailer's decryption.  This can be arranged by
> creating the message something like this:

  Opps, that was me. When I was debugging/testing my anonymous
forwarding/anonymous list software I sent multiple messages before
looking for the reply. (because the software randomly chooses a chain, and
I wasn't sure which remailers introduce a delay)  The problem was that
Encrypted: PGP was only being added for the first remailer in the chain
but the body was being re-encrypted for each remailer.


-- Ray Cromwell        |    Engineering is the implementation of science;    --
-- EE/Math Student     |       politics is the implementation of faith.      --
-- rjc@gnu.ai.mit.edu  |                         - Zetetic Commentaries      --





Thread