[openssl-dev] renegotiation failure causes SSL_shutdown to return 1?

[Judson Wilson]

I am noticing the following sequence of events:

1) SSL_renegotiate(...), followed by SSL_write(..., 0) fails when a web
server rejects it by sending a TCP FIN
2) SSL_get_error returns SSL_ERROR_SSL
3) SSL_in_init(...) is true
4) SSL_shutdown returns 1 <-- this seems strange.

I'm not sure that this is the right behavior.  Shutting down in a handshake
without sending/receiving close_notify shouldn't give the "everything
shutdown gracefully" signal. Perhaps it would be better to return -1 and
signal SSL_ERROR_SSL?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-dev/attachments/20151205/b295fc15/attachment.html>