SSLFilter doesn't support TLS closure (close_notify in RFC 2246) at all. It is required to applications that want to switch between TLS and non-TLS mode.
Description
SSLFilter doesn't support TLS closure (close_notify in RFC 2246) at all. It is required to applications that want to switch between TLS and non-TLS mode.
Related issue: DIRMINA-106 - Add TLS closure support to SSLFilter
* Implemented filterClose() so that close_notify is sent before closing the connection.
* TODO: Provide a way to exchange close_notify in the middle of connection.
Resolving an issue: DIRMINA-106 - Add TLS closure to SSLFilter
* Modified ConntectorTest to test TLS closure
* Added SSLFilter.closeOutbound() to let user send close_notify
* Removed unused flags in SSLHandler
* Added WriteFuture.new(Not)WrittenFuture() method
* Added IoFilterChain.getNextFilter() method
I tested TLS closure work correctly. It worked great.
Resolved issue: DIRMINA-106 - Add TLS closure to SSLFilter
* Now we can revert back to pain-text connection after TLS closure safely.
* Added SSLFilter.startSSL / stopSSL / isSSLStarted to allow users control TLS closure.
Trustin Lee added a comment - 27/Oct/05 04:27 AM SSLFilter now provides three methods:
* startSSL(IoSession)
* stopSSL(IoSession)
* isSSLStarted(IoSession)
Which enables you to implement full StartTLS.
* startSSL(IoSession)
* stopSSL(IoSession)
* isSSLStarted(IoSession)
Which enables you to implement full StartTLS.