1992-10-24 - multiple message destinations

Header Data

From: Eric Hughes <hughes@soda.berkeley.edu>
To: cypherpunks@toad.com
Message Hash: cfed7a111fb65e52097c55e2ea241c10fdb3bcd320dc7febef3af4197e8d3fb0
Message ID: <9210240626.AA08212@soda.berkeley.edu>
Reply To: <9210231806.AA12129@xanadu.xanadu.com>
UTC Datetime: 1992-10-24 06:27:22 UTC
Raw Date: Fri, 23 Oct 92 23:27:22 PDT

Raw message

From: Eric Hughes <hughes@soda.berkeley.edu>
Date: Fri, 23 Oct 92 23:27:22 PDT
To: cypherpunks@toad.com
Subject: multiple message destinations
In-Reply-To: <9210231806.AA12129@xanadu.xanadu.com>
Message-ID: <9210240626.AA08212@soda.berkeley.edu>
MIME-Version: 1.0
Content-Type: text/plain



Dean:
>Are there other ways to handle sending to multiple receivers?

1) You can send it to a service which copies the message and resends
it as many times as you need.  Or send it yourself.

2) You can have the multiple recipients each share a key and let them
trust each other.  (Not recommended for the paranoid).

3) You can use a secret sharing system which is tied to a private key,
such that revealing the secret allows for the derivation of the
private key.  The secret itself is a different private key.  (I'm not
up on the details of these schemes.)

Eric

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)