1994-05-17 - D-H key exchange - how does it work?

Header Data

From: ecarp@netcom.com (Ed Carp)
To: cypherpunks@toad.com
Message Hash: cc42f44c263df5c6c78e1335400275ce3c0ae4ac0d87aaa81006368155eccd29
Message ID: <199405171830.LAA08463@netcom.com>
Reply To: N/A
UTC Datetime: 1994-05-17 18:30:21 UTC
Raw Date: Tue, 17 May 94 11:30:21 PDT

Raw message

From: ecarp@netcom.com (Ed Carp)
Date: Tue, 17 May 94 11:30:21 PDT
To: cypherpunks@toad.com
Subject: D-H key exchange - how does it work?
Message-ID: <199405171830.LAA08463@netcom.com>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----

I browsed through the (SCANT!) documentation that comes with rsaref-2.0. I
didn't find any decent programming examples, just a list of function
calls, which is next to useless without sample code, but that's beside the
point. 

If I understand D-H right, both sides generate public keys from their
private keys, then just exchange public keys.  Is that right?  Or is there
something I'm missing? 
- --
Ed Carp, N7EKG/VE3		ecarp@netcom.com		519/824-3307
Finger ecarp@netcom.com for PGP 2.3a public key		an88744@anon.penet.fi
If you want magic, let go of your armor.  Magic is so much stronger than
steel!        -- Richard Bach, "The Bridge Across Forever"


-----BEGIN PGP SIGNATURE-----
Version: 2.5

iQCVAgUBLdkNCyS9AwzY9LDxAQFW9AP/YeQR0rrX6kfonzLPI5/5U6MB8Q8Uu01a
C9y5y/U2rkYU5gYsAKiw9d4i0yFAiI3KyNWOamdr7aQMWMCOa8y6RPdfKQzuzREg
h4KTjcflcZoffWP7JamboQUPAsOrNwHlumTVnI3cf30U0Zi5QxNHj9PlVupOOvQ4
dSO4Nv6LiG4=
=icYy
-----END PGP SIGNATURE-----




Thread