|
2023-06-21
| ||
| 18:27 | • Ticket [b9d780ee7e] server socket doesn't reply close_notify status still Open with 5 other changes artifact: 2771123a35 user: anonymous | |
| 18:22 | • New ticket [b9d780ee7e]. artifact: 72a80e5d70 user: anonymous | |
| Ticket Hash: | b9d780ee7ec207120b2e586b489dd7985c7372ef | |||
| Title: | server socket doesn't reply close_notify | |||
| Status: | Open | Type: | Incident | |
| Severity: | Critical | Priority: | Immediate | |
| Subsystem: | Resolution: | Open | ||
| Last Modified: | 2023-06-21 18:27:51 | |||
| Version Found In: | tls1.7.21 | |||
| User Comments: | ||||
anonymous added on 2023-06-21 18:22:53:
package require Tcl 8.5.13 Steps: Opening server tls socket (tls::socket) Client connects and tls1.3 handshake completes successfully Data exchanged Server tls socket closed (close) close_notify received from client Server sent [ACK] Client sent [FIN, ACK] Server sent [ACK] Server sent [RST, ACK] Questions: 1) no response to close_notify sent by server? expected? 2) if disabled tls1.3 (i.e. set to false), then also no response to close_notify sent by server? expected? 3) how to fix so that server will respond to client's close_notify | ||||