On 10/03/2015 20:10, Serj Rakitov wrote:
Hi, Jakob. Thanks for reply.
Now I have seen OpenSSL code and something clear for me.
WANT_READ/WANT_WRITE it's just an implementation for WOULDBLOCK: not fatal
error for non-blocking IO. So, for example for socket and Windows it's just
WSAEWOULDBLOCK
Nobody knows?
09.03.2015, 15:30, Serj Rakitov ra...@yandex.com:
I have to open discussion again.
I want to test situations when SSL_read WANT_WRITE and SSL_write WANT_READ.
But I can't do this. SSL_read never wants write and SSL_write never wants
read!
I don't know how to catch
On 09/03/2015 13:21, Serj Rakitov wrote:
I have to open discussion again.
I want to test situations when SSL_read WANT_WRITE and SSL_write WANT_READ. But
I can't do this. SSL_read never wants write and SSL_write never wants read!
I don't know how to catch these situations. I don't know how to
Hi, Jakob. Thanks for reply.
Now I have seen OpenSSL code and something clear for me.
WANT_READ/WANT_WRITE it's just an implementation for WOULDBLOCK: not fatal
error for non-blocking IO. So, for example for socket and Windows it's just
WSAEWOULDBLOCK returns by WSAGetLastError. Peforms by
I have to open discussion again.
I want to test situations when SSL_read WANT_WRITE and SSL_write WANT_READ. But
I can't do this. SSL_read never wants write and SSL_write never wants read!
I don't know how to catch these situations. I don't know how to rehandshake. I
tried after connect and
Thanks, Graham.
Sorry for too late answer ))
Now i am testing...
21.02.2015, 14:42, Graham Leggett minf...@sharp.fm:
On 21 Feb 2015, at 12:58 PM, Serj Rakitov ra...@yandex.com wrote:
I set socket to non-blocking mode.
1. If I do SSL_read() and get result =0 and then SSL_get_error()
On 21 Feb 2015, at 12:58 PM, Serj Rakitov ra...@yandex.com wrote:
I set socket to non-blocking mode.
1. If I do SSL_read() and get result =0 and then SSL_get_error() returns
SSL_ERROR_WANT_WRITE what must I to do?
Is it enough to call SSL_write(ssl,0,0) one time and then again call
