Win/32 Client app using DH keys.
Every so-often a SSL will seem to get stuck in a loop doing the handshake
and call the callback function with the following error:
ProcedureID:UnitCoreDataModule.ssl_infocallback
Description:SSLv3 read server hello A
The message "SSLv3 read server hello A" is th
I have also noticed a leak under Windows/32 using 9.6a. I have started the
task of locating the source of the leak. My memory "tester" says it is
OpenSSL. I have done everything I can to insure that everything is closed
and freed. The best I can get is down to a 4K leak.
I'm not convicned it
emoved.
Since error queue data structures are allocated
automatically for new threads, they must be freed when
threads are terminated in order to avoid memory leaks.
Regards
Bharath
- Original Message -
From: "Scott Frazor" <[EMAIL PROTECTED]>
Date: Thursda
l(SSL_CTX,SSL_CTRL_SET_TMP_DH,0,dh);
Am I way off base here? I have the feeling the SSL_Connect won't handshake
because the DH Key is not set up properly. I simply want to generate
on-the-fly DH keys.
Any feedback would be greatly appreciated.