August 13th, 2013, 03:22 AM

Diffi Hellman need big prime numbers?
Hello!
I am a German native speaker and my English is not perfect. At the moment I study computer science. But now the problem. I have written the Diffi Hellmann key exchange in the language Google Go. I want to understand how Diffi Hellmann works and find out how strong the security is. For this reason I crate the key exchange between Alice and Bob. The attacker Eve catch die public numbers and try to calculate the secret random number of the both senders. Diffi Hellmann use the modulo calculation (g^x mod p) and this make it possible to have different numbers with the same result. I think this is the vulnerability of system. In a test with a loop over x, I find sometime a very low number this matches. I think the prime number (p) must be very big and to find one takes a lot of time. I am right? The only way is to use a big table of prime numbers?
manti7
August 13th, 2013, 11:59 AM

Yes, p must be very large. I think the current recommendation is to use p of at least 2048 bits (about 617 decimal digits). Using even larger p should be more secure, but as p grows larger so does the time needed to compute the DH key exchange. Today, 8192 bits is the maximum option on most systems.
Note that once a size has been chosen, not all primes of that size are suitable. For example, p1 (which will always be composite) must have at least one large factor, where "large" is usually understood to mean at least 256 bits. Suitable prime numbers are often called strong primes.
There are fairly efficient tests for pseudoprimality testing, which make it possible to find an arbitrary 2048bit strong prime within a few minutes on an ordinary computer. However, the process is a little complicated, involving several steps and techniques.
Once p has been found, it is also necessary to find a generator (also called a primitive root) g, with large order in p. For a large p, there are very many such generators, and for DiffieHellman, one is as good as another. Some DH groups use g=2; others use large g (for example, 256 bits in length, or even as large as p). For DH, the size of g has little practical importance.
Finding a generator depends on how the prime p has been constructed. It requires knowing the factorization of p1. If p were chosen at random, factoring p1 would in general not be feasible, but p is always chosen so that at least some of the factors of p1 are known: this is necessary to ensure that there is at least one large factor.
With knowledge of the factors of p1, an arbitrary integer can quickly be tested to determine whether it is a generator of sufficiently large group size.
However, it isn't necessary to go the work of finding a suitable p and g. With DiffieHellman, the group (specified by p and g) is not secret. Further, there is no security advantage to using a different group from anybody else. For example, suppose that in the world, there are 500 million computers whose users accept the security level of a 2048bit p with a subgroup of 256 bits. It is absolutely fine for all of them to use the same group!
For this reason, various DH groups have been published for anyone to use. These groups have been checked for suitable properties, and some have p specially chosen to make the computations a little faster. You can look up one of these and use it!
Here is an example:
IETF RFC 5114 (see "2.3. 2048bit MODP Group with 256bit Prime Order Subgroup")
Last edited by mah$us; August 23rd, 2013 at 03:32 AM.
Reason: corrected typographical error
August 16th, 2013, 09:53 AM

Hello mah$us!
Thank you for your nice post. The solution is the Prime Order Subgroup. In the next time I try to implement this in my test program.
manti7