Norman Maurer a71ec15fc4 Correctly use HandshakeStatus.NEED_WRAP when a handshake failed and a alert was produced (#11412) ... Motivation: We need to ensure we always "consumed" all alerts etc via SSLEngine.wrap(...) before we teardown the engine. Failing to do so may lead to a situation where the remote peer will not be able to see the actual cause of the handshake failure but just see the connection being closed. Modifications: Correctly return HandshakeStatus.NEED_WRAP when we need to wrap some data first before we shutdown the engine because of a handshake failure. Result: Fixes https://github.com/netty/netty/issues/11388		2021-06-24 10:05:47 +02:00
..
src	Correctly use HandshakeStatus.NEED_WRAP when a handshake failed and a alert was produced (#11412)	2021-06-24 10:05:47 +02:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2021-05-19 12:09:18 +00:00