Hi Scott, Scott <cheesy4poofs@cox.net> wrote:

I wish I had better news to report, but it's still zero.

Well, here's what the man page for SSL_get_error has to say about SSL_ERROR_SYSCALL: Some I/O error occurred. The OpenSSL error queue may contain more information on the error. If the error queue is empty (i.e. ERR_get_error() returns 0), ret can be used to find out more about the error: If ret == 0, an EOF was observed that violates the protocol. If ret == -1, the underlying BIO reported an I/O error (for socket I/O on Unix systems, consult errno for details). So, can you please check what the value of rc is when the problem occurs. It may be that the connection is being closed by the peer when the SSL engine is not expecting it (or possibly a bug in openssl_operation that means it erroneously reports EOF to the SSL engine). Cheers, Chris