Overview
| Artifact ID: | e4f8b328edae141042f1a8e5a9413c7c2de82189f737a03465291e12f97b8b57 | 
|---|---|
| Ticket: | 657abb4cd1f8f1032731ee0366c7cc643af778e7 TLS Socket Closed in Child Process | 
| User & Date: | bohagan on 2025-10-11 22:58:49 | 
Changes
- icomment:
Part of the confusion is TLS is not a socket connection, but a protocol on top of it. So if the TLS session is "shutdown" in the child, it is no longer available in the parent. However, the channel itself may remain available if tls::unimport is used instead of close, but the TLS session is itself terminated. This assumes the other end doesn't close the socket when it receives the close_notify. 
- login: "bohagan"
- mimetype: "text/x-fossil-plain"
- resolution changed to: "Works_As_Designed"
- status changed to: "Closed"