1995-11-07 - encrypt-key remailers

Header Data

From: Jennifer Mansfield-Jones <cardtris@umich.edu>
To: cypherpunks@toad.com
Message Hash: 548bfd631cf96b6d664e783a9bc633d307f3398aa9a2688447e2907e3551aba3
Message ID: <Pine.SOL.3.91.951107143109.23860A-100000@gorf.rs.itd.umich.edu>
Reply To: N/A
UTC Datetime: 1995-11-07 20:40:34 UTC
Raw Date: Wed, 8 Nov 1995 04:40:34 +0800

Raw message

From: Jennifer Mansfield-Jones <cardtris@umich.edu>
Date: Wed, 8 Nov 1995 04:40:34 +0800
To: cypherpunks@toad.com
Subject: encrypt-key remailers
Message-ID: <Pine.SOL.3.91.951107143109.23860A-100000@gorf.rs.itd.umich.edu>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----

Hello, all -- 

I've a semi-clueless question for the gurus here.  I'm trying to
use the Encrypt-Key option on some of the mixmaster (type I)
cypherpunks remailers, and running into trouble.

Please pardon the level of gory detail here; I'm at a loss to
see what I'm missing, so I present a verbatim record of what I
have tried so far.  Consider the sample remailing directions
below.  The remailer-help documents include very similar
examples.  The single-space indenting is only to indicate where
files are included, and avoid complaints from pgp-aware mail
handlers.

 ::
 Encrypt-Key: apasswd
 Request-Remailing-To: cardtris@umich.edu
 Subject: reply-block-test

 **



The above gets encrypted with flame's public key, yielding a
normal little PGP message.

The block gets 

 ::
 Encrypted: PGP

Prepended onto it, and the result looks like:

 ::
 Encrypted: PGP
 
 -----BEGIN PGP MESSAGE-----
 Version: 2.6.2

 hIwDQyA95PVgp+UBA/4/Vm0EMi2BYBCioaLe35qx1rOxQVGEYoulmwjdDtFsXTup
 L08nyycNVIdxIAW5O+0T4kVuV3/ycAd84SmxDAls9n5Ebc6vP+gwE+dWCaY1TNok
 1Ju08hheCJ2nC0piiN/eT0eR646fMvKGI1CiitBKXPSSkPT6alYlQvLPxd+uV6YA
 AACBvZthKwNEb5DQg/5otGH3njgrJISEyvgEKDZaMFuOUPzxk4IZ4NXm0v2cgHVz
 yxMelKz4WHnOylmZ3WWTFmngukIdasIiFf5avRZ/A4Ff1FRXf7SpxvTfGpA4pYPE
 yjmFhsw/NCnRVqBAH65MiU0USQhPZkZDwLe6spBaJpxENq5C
 =/tbc
 -----END PGP MESSAGE-----
 
 
Trying the above, I find that it does *sort of* work as a reply
block.  If I append sample text and send everything to
remailer@flame.alias.net, I get a reply back that looks like, for
instance: 

Date: Mon, 6 Nov 1995 19:22:13 +0100
From: Anonymous <nobody@flame.alias.net>
To: cardtris@umich.edu
Subject: reply-block-test

**


The appended text, which I expected to come back conventionally
encrypted with 'apasswd', has just vanished into the void.  
Obviously I'm missing something... probably something that seemed 
painfully obvious to the writer of the remailer help file.  If I 
omit the encryption key and '**', I can get reply blocks to work fine,
even chained through multiple remailers.  Suggestions?

   many thanks,

                                   -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
  Dept. of Biology                         Jennifer Mansfield-Jones
 University of Michigan                           cardtris@umich.edu
http://www-personal.umich.edu/~cardtris/cardtris.htm
                                             ^---- PGP key available

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBMJ5ueHTZ8yRAewEFAQEewgP/U3OhcBaKSjd1Jpg51UX7NMD3SfrF56WI
fQExYw1lG70GqfEko9T1ft89mDJlj1IvjToR6TJPws8P919Y2qikw333wCt6A9eR
pTMf2Jy1OjKwXRIqlFtrIMky+X2jUYDSMk3H+U1IwT7jjJUfVtzPuSEia0ZzFGmi
U5BLQvrLamQ=
=z1yS
-----END PGP SIGNATURE-----





Thread