1992-10-24 - multiple message destinations

Header Data

From: tribble@xanadu.com (E. Dean Tribble)
To: uunet!soda.berkeley.edu!hughes@uunet.UU.NET
Message Hash: 8de813733f4767b35683f1b680f8fdb5fd2a9f279f4c87fc9d9444001b7eb551
Message ID: <9210240854.AA15621@xanadu.xanadu.com>
Reply To: <9210240626.AA08212@soda.berkeley.edu>
UTC Datetime: 1992-10-24 09:31:19 UTC
Raw Date: Sat, 24 Oct 92 02:31:19 PDT

Raw message

From: tribble@xanadu.com (E. Dean Tribble)
Date: Sat, 24 Oct 92 02:31:19 PDT
To: uunet!soda.berkeley.edu!hughes@uunet.UU.NET
Subject: multiple message destinations
In-Reply-To: <9210240626.AA08212@soda.berkeley.edu>
Message-ID: <9210240854.AA15621@xanadu.xanadu.com>
MIME-Version: 1.0
Content-Type: text/plain


Doies the scheme I suggested (and I'm sure is not original) work?
Using all the various private keys to encrypt a single cypher key that
the rest of the message is encrypted with?

dean

Thread

• Return to October 1992

• Return to “Eric Hughes <hughes@soda.berkeley.edu>”
• Return to “pmetzger@shearson.com (Perry E. Metzger)”

• Return to “tribble@xanadu.com (E. Dean Tribble)”

• 1992-10-23 (Fri, 23 Oct 92 14:41:59 PDT) - multiple message destinations - tribble@xanadu.com (E. Dean Tribble)
  • 1992-10-24 (Fri, 23 Oct 92 23:27:22 PDT) - multiple message destinations - Eric Hughes <hughes@soda.berkeley.edu>
    • 1992-10-24 (Sat, 24 Oct 92 02:31:19 PDT) - multiple message destinations - tribble@xanadu.com (E. Dean Tribble)
      • 1992-10-24 (Sat, 24 Oct 92 09:24:30 PDT) - multiple message destinations - Eric Hughes <hughes@soda.berkeley.edu>
  • 1992-10-25 (Sat, 24 Oct 92 19:34:56 PDT) - multiple message destinations - pmetzger@shearson.com (Perry E. Metzger)