Context:

Openssl 102k
ATS 714

I notice that at times a client will send a TLS 1.2 close-notify,
immediately followed by a FIN-ACK. Which seems to be following spec.

"It is not required for the initiator of the close to wait for the
responding close_notify alert before
   closing the read side of the connection."


However, in response, ATS continuous to send 'application data'
instead of issuing its own TLS 1.2 close-notify. Which then results in
connections lingering waiting for an ACK back from the client.
Which will never come, since per spec:

"Any data received after a closure alert is ignored."


Is ATS still within TLS 1.2 spec by continuing to send application
data, even though the client sent a close notify ?

I tested some other https servers compiled against openssl 102k, and I
see a close notify sent by the client, with the https server
responding with it's own close notify.

Thanks!

Reply via email to