1993-06-01 - No Subject

Header Data

From: Eric Hughes <hughes@soda.berkeley.edu>
To: cypherpunks@toad.com
Message Hash: a6d406b8c92c04bfa13a225740798497e9bbd796fca3d88ed608b9f84dc8f898
Message ID: <9306011614.AA16663@soda.berkeley.edu>
Reply To: <199306010527.AA00963@xtropia>
UTC Datetime: 1993-06-01 15:41:02 UTC
Raw Date: Tue, 1 Jun 93 08:41:02 PDT

Raw message

From: Eric Hughes <hughes@soda.berkeley.edu>
Date: Tue, 1 Jun 93 08:41:02 PDT
To: cypherpunks@toad.com
Subject: No Subject
In-Reply-To: <199306010527.AA00963@xtropia>
Message-ID: <9306011614.AA16663@soda.berkeley.edu>
MIME-Version: 1.0
Content-Type: text/plain


>This means that the pass phrase [for the remailer secret key] has to
>exist, in the clear, in the scripts which implement the remailer.

Currently that is the easiest way, to be sure.  Another way would be
to store the passphrase encrypted in a file so that at least it's not
findable with strings(1).  Here a quick hack for someone who's looking
for a project: a passphrase storage process which accepts requests
from a slightly modified PGP.

Hal's basic point, however is not mitigated.  Nothing is secure from a
clever root.

>Perhaps Karl could add a notation in his
>remailer lists about which machines are public and which are private.  

An excellent suggestion.

Eric





Thread