Thanks, this did the trick...
Is there any way to indicate that a BIO does not support blocking IO? The
exact situation is a bit odd, writes always block, but reads are always
non-blocking... This seems to work fine, but I wonder if there is a way to
indicate this behaviour to the user. For examp
On Sun, Mar 13, 2011, Keean Schupke wrote:
> I have a custom BIO that I want to be non-blocking. Currently when calling
> SSL_connect when using this BIO, it is returning -1, but
> calling SSL_get_error after does not return SSL_ERROR_WANT_READ
> nor SSL_ERROR_WANT_WRITE.
>
> How does my custom B
