History Of Ticket b9d780ee7ec207120b2e586b489dd7985c7372ef

Artifacts Associated With Ticket b9d780ee7ec207120b2e586b489dd7985c7372ef

  1. Ticket change [72a80e5d70] (rid 1588) by anonymous on 2023-06-21 18:22:53:

    1. foundin initialized to: "tls1.7.21"
    2. icomment:
      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
      
    3. login: "anonymous"
    4. mimetype: "text/x-fossil-plain"
    5. private_contact initialized to: "5611adc9c2fc60cdb17b54ba4012f3376e47b161"
    6. severity initialized to: "Critical"
    7. status initialized to: "Open"
    8. type initialized to: "Incident"
  2. Ticket change [2771123a35] (rid 1587) by anonymous on 2023-06-21 18:27:51:

    1. login: "anonymous"
    2. mimetype: "text/x-fossil-plain"
    3. priority changed to: "Immediate"
    4. resolution changed to: "Open"
    5. title changed to: "server socket doesn't reply close_notify"