Le 5/13/13 10:30 PM, Jeff MAURY a écrit : > Hi, > > As I'm reading the TLS specs, I noticed that the processing of the close > alarm, if not critical, may leave the underlaying transport connection > (socket) open, probably to deal with STARTTLS behavior. Yes.
> So one option would be to had two new events: Secured (end of handshake) > and Unsecured (Non critical Close alarm received). We have flags in the session which can be set to tell if the session is secured or not. Do we really need two events to be propagated to the IoHandler ? > Another pro is that in case of re-handshake, the application can now be > notified. That's a good use case. > By the way, do you know how the critical flag is given back by the > SLLEngine ? My understanding is that the close alert results in the SSLEngine to change the SSLEngineResult status to CLOSED. -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
