1995-11-14 - Re: 4096 bit strong prime for Diffle-Hellman

Header Data

From: Eric Young <eay@mincom.oz.au>
To: cypherpunks@toad.com
Message Hash: 2deb71ea7f44f9da6077b98ec4d592b66020187e42af1bdea435851df443a4f0
Message ID: <Pine.SOL.3.91.951114105404.13469A-100000@orb>
Reply To: <Pine.SOL.3.91.951114090156.23102A-100000@orb>
UTC Datetime: 1995-11-14 17:15:26 UTC
Raw Date: Wed, 15 Nov 1995 01:15:26 +0800

Raw message

From: Eric Young <eay@mincom.oz.au>
Date: Wed, 15 Nov 1995 01:15:26 +0800
To: cypherpunks@toad.com
Subject: Re: 4096 bit strong prime for Diffle-Hellman
In-Reply-To: <Pine.SOL.3.91.951114090156.23102A-100000@orb>
Message-ID: <Pine.SOL.3.91.951114105404.13469A-100000@orb>
MIME-Version: 1.0
Content-Type: text/plain



On Tue, 14 Nov 1995, Eric Young wrote:
> Even if the private DH values are pre-calculated, this will only halve the
> time of the DH operation and if this is done it looses the advantage of DH
> in that if the private/public pair are 'generated on the fly',
> pre-recorded session will not be able to be decoded if the private key is

Urk, that reads very badly what I ment is that since a different
public/private key is used per session, if a private key is revealed, any
previous and future comunication between the 2 entities is not
compromised, only the particular session using that public/private key pair.
Also since the key pair is generated on the fly, they don't need to be 
recorded on disk etc, so they only way to get the private key is to 
'hack' the application at runtime (or modify it in advance).

eric (who is have a bad day converting his thoughts to english...).





Thread