1993-07-14 - Re: Secure comm program, Sockets + LINK

Header Data

From: “Perry E. Metzger” <pmetzger@lehman.com>
To: cypherpunks@toad.com
Message Hash: 2ddf30124da53035462da9c635579bc4e051a8cd4cb39ed0eae1845f8e4d8d1c
Message ID: <9307141600.AA28360@snark.shearson.com>
Reply To: <9307132043.aa10612@hermix.markv.com>
UTC Datetime: 1993-07-14 16:01:14 UTC
Raw Date: Wed, 14 Jul 93 09:01:14 PDT

Raw message

From: "Perry E. Metzger" <pmetzger@lehman.com>
Date: Wed, 14 Jul 93 09:01:14 PDT
To: cypherpunks@toad.com
Subject: Re: Secure comm program, Sockets + LINK
In-Reply-To: <9307132043.aa10612@hermix.markv.com>
Message-ID: <9307141600.AA28360@snark.shearson.com>
MIME-Version: 1.0
Content-Type: text/plain



jpp@markv.com says:
>   The bootstrap problem (how you get the public key to the machine
> with only unsecure chanels at your disposal) is interesting though.  I
> wonder if it can be solved without DH key exchange?

You can't even solve the problem with DH key exchange -- you are
subject to "man in the middle" attacks. You must share SOME
information via a secure channel in order to have both authentication
and privacy on a channel. However, the information exchanged could be
small and fairly one-time -- like the public key of a trusted entity
that signs other public keys.

Perry





Thread