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 njs
Recipients alex, christian.heimes, dstufft, janssen, martin.panter, njs
Date 2017-09-06.17:43:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
My reading of the man page is that if SSL_shutdown returns 0, this means that it succeeded at doing the first phase of shutdown. If there are errors then they should be ignored, because it actually succeeded.

If you want to then complete the second phase of shutdown, of course, you have to call it again, but that's no different than any other use of SSL_shutdown.

If two calls to SSL_shutdown both return zero, then that's definitely a bug in OpenSSL. A return value of zero means that previously the SSL_SENT_SHUTDOWN flag was not set, and now it is set, so that can only happen once per connection. But that's orthogonal to the SSL_ERROR_SYSCALL issue.
Date User Action Args
2017-09-06 17:43:18njssetrecipients: + njs, janssen, christian.heimes, alex, martin.panter, dstufft
2017-09-06 17:43:18njssetmessageid: <>
2017-09-06 17:43:18njslinkissue30437 messages
2017-09-06 17:43:18njscreate