Re: [openssl-users] SSL_read, SSL_write error handling

I did find a very good explanation here: https://mta.openssl.org/pipermail/openssl-users/2015-March/000709.html The idea of "what SSL wants" and "what the app wants" is a very good explanation. This is the pseudocode I'm working with currently: io_callback(events) { if

Re: [openssl-users] SSL_read, SSL_write error handling

On Thu, Sep 15, 2016 at 05:07:22AM +0200, Alex Hultman wrote: > If SSL_write returns the error SSL_ERROR_WANT_READ, am I then allowed to > call SSL_read before I have called SSL_write? WANT_READ means that OpenSSL *internally* needs to read some (often ciphertext) bytes from the peer, and that

[openssl-users] SSL_read, SSL_write error handling

If SSL_write returns the error SSL_ERROR_WANT_READ, am I then allowed to call SSL_read before I have called SSL_write? What I'm trying to figure out is, can I handle SSL_ERROR_WANT_READ with one or many calls to SSL_read, and can I handle SSL_ERROR_WANT_WRITE with one or many calls to SSL_write -

[openssl-users] openssl crl fails to parse a CRL file, which seems correct

Hi, (this is a resend because my MUA crashed while I tried to send this mail earlier. If you get it twice, my apologies) When I try to parse some of the CRLs at , I sometimes get this error: wouter@gangtai:~$ openssl version OpenSSL 1.0.2h 3 May 2016

Re: [openssl-users] openssl-1.0.2i?

On 13/09/16 21:00, Marek Svent wrote: > Hi, > > 1.0.2h was released four months ago and although several security issues > worth for CVE number is discovered in it and there has been a lot of > commits in the 1.0.2 branch fixing other important issues, there is no > sign of 1.0.2i. Is it