Exactly what david says...
why would you want to risk data loss ??
Lokesh.
On 6/2/05, Gayathri Sundar [EMAIL PROTECTED] wrote:
Hi,
What I think is as its the application's responsibility to retry
the same openssl operation whenever it receives a WANT_READ or
WANT_WRITE, why cant we
Learning it the HARD way... :))
anyways...
doesn't matter if its 0.9.6 or later it should go non-blocking.
SSL_renegotiate_pending only checks if the handshake is succesfull by verifying
state flag in SSL structure. It doesnt deal with BIOs or TCP Buffers.
SSL_do_handshake enforces the REAL
HI,
SSL_accept/SSL_connect is something that we use to establish an
initial SSL connection and we use SSL-renegotiate/SSL_do_handshake
based on timers
we install for SSL for re-negotiating KEYs such that hacking the SSL
connection is robust.
Having said that.. I assume you already have an SSL
HI,
Pls check man page of SSL_load_verify_locations(...) which can be used
in writing the server or client program.
-Lokesh.
On 6/1/05, Vaclav Stepan [EMAIL PROTECTED] wrote:
Hi,
I ran in trouble with the following thing. There is a Debian woody,
with OpenSSL 0.9.6c installed. I am trying
HI,
You may want to consider using SSL_CTX_set_mode(...)
with SSL_MODE_AUTO_RETRY flag such that you would'nt recieve
SSL_ERROR_WANT_XXX messages.
Normally those messages come when the other side requests for re-negotiation.
-Lokesh.
On 5/31/05, opt [EMAIL PROTECTED] wrote:
Hi everyone
I
Hello There.
I wrote Client and Server Programs using SSL.
They fail to hand-shake when I use self Signed Certificates and
succeed when I use Certificates generated from a CA.
The failure I get when using self Signed Certificate is ...
4904:error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1
