s6-networking/doc/s6-tlsc-io.html, branch v2.8.0.1

Implement --no-verify-cert for s6-tlsc and s6-tlsc-io

2026-04-13T03:32:51Z

Update deps/docs/mirrors

2026-04-04T16:10:58Z

Add -J and -j to the TLS tools to check for peer close_notify.

2023-11-16T05:13:06Z

Also, and more importantly, significantly rewrite stls_run() for better full-duplex support. This implementation isn't fully tested yet. Signed-off-by: Laurent Bercot

New and fixed version of sbearssl_run

2023-11-11T23:55:28Z

Signed-off-by: Laurent Bercot

Prepare for 2.7.0.0. Better s6-tlsc-io interface.

2023-11-10T11:28:19Z

Signed-off-by: Laurent Bercot

Doc fixes, thanks flexibeast

2021-02-04T10:37:39Z

Remove SSL_TLS_SNI_SERVERNAME (instead of defined but empty) if no SNI

2021-01-28T14:31:38Z

Prepare for 2.4.1.0; add SSL_TLS_SNI_SERVERNAME

2021-01-28T13:17:25Z

Implement handshake timeout for libtls backend

2021-01-13T11:36:16Z

Change -K semantics: timeout during handshake, not afterwards

2020-12-07T12:53:54Z

- the TLS tunnel itself should be transparent so it has no business shutting down the connection no matter how long the app takes - there's still an undetectable situation on some kernels where EOF doesn't get transmitted from the network, and the engine is in the handshake, and it can't do anything but wait forever. A timeout is useful here: dawg, your peer is never going to send any more data, you should just give up. - if the situation happens after the handshake, the *app* should have a timeout and die. The tunnel will follow suit. - libtls has a blocking tls_handshake() blackbox, we cannot give it a timeout. Too bad, use bearssl.