This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author joernheissler
Recipients alex, christian.heimes, docs@python, dstufft, janssen, joernheissler, njs, slingamn
Date 2019-12-23.18:47:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1577126853.56.0.652495588592.issue31711@roundup.psfhosted.org>
In-reply-to
Content
Manpage (openssl 1.1.1d) now states:

You should not call SSL_write() with num=0, it will return an error.  SSL_write_ex() can be called with num=0, but will not send application data to the peer. SSL_write_ex was added in 1.1.1

So it looks like openssl cleaned up another mistake by defining SSL_write_ex's behaviour to be a noop.
History
Date User Action Args
2019-12-23 18:47:33joernheisslersetrecipients: + joernheissler, janssen, christian.heimes, alex, njs, docs@python, slingamn, dstufft
2019-12-23 18:47:33joernheisslersetmessageid: <1577126853.56.0.652495588592.issue31711@roundup.psfhosted.org>
2019-12-23 18:47:33joernheisslerlinkissue31711 messages
2019-12-23 18:47:33joernheisslercreate