Matt Caswell f73c737c7a Handle SSL_shutdown while in init more appropriately
Calling SSL_shutdown while in init previously gave a "1" response, meaning
everything was successfully closed down (even though it wasn't). Better is
to send our close_notify, but fail when trying to receive one.

The problem with doing a shutdown while in the middle of a handshake is
that once our close_notify is sent we shouldn't really do anything else
(including process handshake/CCS messages) until we've received a
close_notify back from the peer. However the peer might send a CCS before
acting on our close_notify - so we won't be able to read it because we're
not acting on CCS messages!

Reviewed-by: Viktor Dukhovni <viktor@openssl.org>
2016-01-20 13:55:36 +00:00
..
2015-09-20 14:21:18 +01:00
2015-08-28 11:59:23 -04:00
2015-03-19 11:11:22 +00:00
2015-05-22 09:44:44 +01:00
2015-02-27 20:31:28 +00:00
2015-09-02 00:37:58 +01:00
2015-07-30 10:18:43 +01:00
2015-09-02 00:29:00 +01:00
2015-01-22 09:31:38 +00:00
2015-01-22 09:31:38 +00:00
2015-01-22 09:31:38 +00:00
2015-01-22 09:31:38 +00:00
2015-11-24 21:54:38 +01:00
2015-05-05 19:50:12 +01:00
2015-01-07 02:15:35 +01:00
2015-12-19 14:44:03 +00:00
2015-10-23 20:32:58 +02:00
2015-04-16 13:50:01 -04:00