summaryrefslogtreecommitdiff
path: root/doc/libstls/index.html
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2023-11-20 05:13:06 +0000
committerLaurent Bercot <ska@appnovation.com>2023-11-20 05:13:06 +0000
commit9c4a097d900fb623abeb61d3a58cf58e9c5f383f (patch)
treee616efc1b33fcd984d1599b8b7f4473acc2ca779 /doc/libstls/index.html
parent60b4d9d032509de8395b5c8131c36327f020946f (diff)
downloads6-networking-9c4a097d900fb623abeb61d3a58cf58e9c5f383f.tar.xz
Update documentation; make s6-tlsd-io more conservative by default
Signed-off-by: Laurent Bercot <ska@appnovation.com>
Diffstat (limited to 'doc/libstls/index.html')
-rw-r--r--doc/libstls/index.html6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/libstls/index.html b/doc/libstls/index.html
index c1bb833..4abafa7 100644
--- a/doc/libstls/index.html
+++ b/doc/libstls/index.html
@@ -175,6 +175,12 @@ separate closing of both ways. EOF allows full-duplex until the
very end, but is insecure if the application protocol does not
know in advance how many bytes it should get. Modern application
protocols should all work with EOF. </li>
+ <li> bit 1 tells the engine whether (if set) or not (if clear) to
+be sensitive to close_notify if on the <em>receiving</em> side of them.
+If set, if the peer closes the connection without sending a close_notify,
+the process will exit 98 with a fatal error message. If clear, the EOF
+will be transmitted and the engine will continue serving the other half
+of the connection until it's closed as well, and the process wil exit 0. </li>
</ul> </li>
<li> <em>tto</em> is a pointer to a
<a href="//skarnet.org/software/skalibs/libstddjb/tai.html">tain_t</a>