I've found out that it's related to how SSL_Write() expects the same
buffer pointer after an SSL_ERROR_WANT_WRITE occurs.
I also found out that this can be avoided by issuing a SSL_ctrl() which
I tried, but now I get corrupted data from certain point.
How EXACTLY is SSL_Write in non-blocking mode different from
non-blocking write()/send()?
If it fails with SSL_ERROR_WANT_WRITE does it expect that the next call
the buffer will be 100% same? Can there be additional data added to the
buffer in between?
Ales
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]
