] On Behalf Of Xiaoyu Ruan
Sent: Thursday, March 01, 2007 15:30
To: openssl-users@openssl.org
Subject: RE: Question about Diffie-Hellma
Here is how DH works:
1. server determines p, q, sends p and q to client.
2. server selects a random number priv_key_s, computes pub_key_s =
q
On Fri, Mar 02, 2007 at 09:24:27AM -0600, Dinh, Thao V CIV NSWCDD, K72 wrote:
I have a cipher suit :
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
What is It meant TLS_DHE_RSA Combine between RSA with
$ openssl ciphers -v kEDH+aRSA+3DES+SHA
EDH-RSA-DES-CBC3-SHASSLv3 Kx=DH
, March 01, 2007 15:30
To: openssl-users@openssl.org
Subject: RE: Question about Diffie-Hellma
Here is how DH works:
1. server determines p, q, sends p and q to client.
2. server selects a random number priv_key_s, computes pub_key_s =
q^priv_key_s mod p, sends pub_key_s to client.
3
Hello,
I have a cipher suit :
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
What is It meant TLS_DHE_RSA Combine between RSA with
Diffie-Hellman ?? RSA is key transport. DH is key agreement. How do they
use together ?? Please help.
When we use Ephemeral DH, we need to use a (RSA or
Hi All
I have a hard time to understand Diffie-Hellia Key agreement. This is a
DH structure
Typedef structure dh_st
{
BEGIUM *p;
BEGIUM *q;
BEGIUM *pub_key;
BEGIUM *priv_key;
}
According to Openssl Book p and q, each pair chooses a random large
integer priv_key member. A value for
: Question about Diffie-Hellma
Hi All
I have a hard time to understand Diffie-Hellia Key agreement. This is a
DH structure
Typedef structure dh_st
{
BEGIUM *p;
BEGIUM *q;
BEGIUM *pub_key;
BEGIUM *priv_key;
}
According to Openssl Book p and q, each pair chooses a random large
Thank You very much Xiaoyu
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Xiaoyu Ruan
Sent: Thursday, March 01, 2007 15:30
To: openssl-users@openssl.org
Subject: RE: Question about Diffie-Hellma
Here is how DH works:
1. server determines p, q
On 2007.03.01 at 14:12:55 -0600, Dinh, Thao V CIV NSWCDD, K72 wrote:
Questions:
1) each peer can independently compute the shared secrete What is
meant ?? Client has one shared key, Server has different shared key???
It is meant that only public keys are transferred over
