From: “A. Padgett Peterson, P.E. Information Security” <PADGETT@hobbes.orl.mmc.com>
To: cypherpunks@toad.com
Message Hash: c2da2e22f4c3ac66211b1c1ee90e764de76d08079c8fe0e856544750107134db
Message ID: <960205000641.202190a1@hobbes.orl.mmc.com>
Reply To: N/A
UTC Datetime: 1996-02-05 05:58:37 UTC
Raw Date: Mon, 5 Feb 1996 13:58:37 +0800
From: "A. Padgett Peterson, P.E. Information Security" <PADGETT@hobbes.orl.mmc.com>
Date: Mon, 5 Feb 1996 13:58:37 +0800
To: cypherpunks@toad.com
Subject: The Story Lady
Message-ID: <960205000641.202190a1@hobbes.orl.mmc.com>
MIME-Version: 1.0
Content-Type: text/plain
>> Let me see if I understand this concept correctly. The remote site would
>> pre-encrypt the transmitted data, so that when received it could be
>> decrypted by the requestor according to his (or a temporarily chosen, to
>> avoid disclosing the actual recipient.) public key, so as to disguise both
>> the material and perhaps also the actual requestor?
>Something like that, yes.
As the quote went "It goes something like this...Not *exactly* like this
but something...".
What netscape does is to receive a signed public key, encrypt the session key,
& return *that*. The session is then encrypted with a fast symmetric algo.
(RC4-40 Netsape/export, IDEA - PGP). So PGP/scape would do exactly the same
thing with trivial changes to the monkey-motion.
Now Government approved PGP/BE - something to strive for 8*).
warmly,
Padgett
Return to February 1996
Return to ““A. Padgett Peterson, P.E. Information Security” <PADGETT@hobbes.orl.mmc.com>”
1996-02-05 (Mon, 5 Feb 1996 13:58:37 +0800) - The Story Lady - “A. Padgett Peterson, P.E. Information Security” <PADGETT@hobbes.orl.mmc.com>