On 11 Jul 2011, at 3:18 PM, Carla Strembicke wrote:
The server recieves the encrypted data and sends to the lower level and
where it is pumped into the SSL structure ( which is using these memory
buffers) using the BIO_write call ( I acutally see that bytes are written
into it) and the
Hi,
I need help deciphering why I am getting this error.
Below is the scenario which is not a common implementation ( well not that I
have been able to fine on the net).
What I am doing is using bio memory buffers (BIO_s_mem() ) at an embedded
level away from the connection( currently tcpip).
So
On 7/11/2011 3:18 PM, Carla Strembicke wrote:
The server recieves the encrypted data and sends to the lower level
and where it is pumped into the SSL structure ( which is using these
memory buffers) using the BIO_write call ( I acutally see that bytes are
written into it) and the buffer looks
Hi all!
Im having a problem with SSL_read. When SSL_read fails and returns
SSL_ERROR_WANT_READ I do select checking for readability but I never get a
hit and if I try SSL_read again I get the same error. Does anyone know what
to do?
Im using different threads for receiving and sending.
Im having a problem with SSL_read. When SSL_read fails and returns
SSL_ERROR_WANT_READ I do select checking for readability but I
never get a
hit and if I try SSL_read again I get the same error. Does anyone
know what
to do?
That sounds like there is just nothing to read.
Im
David Schwartz wrote:
Make sure that you protect the SSL session with a
mutex. You are not allowed to call SSL_read and SSL_write at the same time
on the same session from different threads.
DS
David,
Does same session mean, same instance of an ssl object, or same
instance of a
David,
Does same session mean, same instance of an ssl object, or same
instance of a ctx object?
You are permitted concurrent access to different SSL sessions based on
the
same context. You just cannot read and write to the same session at the same
time. (You also can't read a
