Dear All;
When I compiled openssl-0.9.8g on VDSP and run \demos\ssl\cli.cpp .And I
tried to connect https://www.gmail.com https://www.gmail.com/ .At that
time I saw client sent client hello and server sent server hello
successfully. But After that Client is not sending MASTER_KEY message. I
Dear All;
When I compiled openssl-0.9.8g on VDSP and run \demos\ssl\cli.cpp .And I
tried to connect https://www.gmail.com https://www.gmail.com/ using
sslv2.0 .At that time I saw client sent client hello and server sent
server hello successfully. But After that Client was not sending
It's rather infeasable to keep the same private key and generate a new
public key. If you keep the private key after the expiration of the
certificate, you can still decrypt messages encrypted to it; thus, if
you generate a new pub/priv pair, you just need to keep the old key,
and use all the
Hello,
When I compiled openssl-0.9.8g on VDSP and run \demos\ssl\cli.cpp .And I
tried to connect
https://www.gmail.com using sslv2.0 .At that time I saw client sent
client hello and
server sent server hello successfully. But After that Client was not
sending MASTER_KEY
message. I
On Saturday 15 March 2008, Kyle Hamilton wrote:
It's rather infeasable to keep the same private key and generate a new
public key. If you keep the private key after the expiration of the
certificate, you can still decrypt messages encrypted to it; thus, if
you generate a new pub/priv pair,
On Sat, Mar 15, 2008 at 12:12 PM, Mick [EMAIL PROTECTED] wrote:
On Saturday 15 March 2008, Kyle Hamilton wrote:
It's rather infeasable to keep the same private key and generate a new
public key. If you keep the private key after the expiration of the
certificate, you can still decrypt
