| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2021-11-18 | Allow SNI wildcarding for *.example.com | Laurent Bercot | |
| Signed-off-by: Laurent Bercot <ska@appnovation.com> | |||
| 2021-05-28 | Server-side SNI, libtls version | Laurent Bercot | |
| Implementation for bearssl coming soon. | |||
| 2021-05-18 | Prepare for 2.4.2.0; implement client certificates with bearssl | Laurent Bercot | |
| Also send a bit more environment with libtls | |||
| 2021-02-16 | More doc fixes | Laurent Bercot | |
| 2021-02-04 | More doc fixes | Laurent Bercot | |
| 2021-01-28 | Remove SSL_TLS_SNI_SERVERNAME (instead of defined but empty) if no SNI | Laurent Bercot | |
| 2021-01-28 | Prepare for 2.4.1.0; add SSL_TLS_SNI_SERVERNAME | Laurent Bercot | |
| 2021-01-13 | Implement handshake timeout for libtls backend | Laurent Bercot | |
| 2020-12-07 | Change -K semantics: timeout *during handshake*, not afterwards | Laurent Bercot | |
| - 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. | |||
| 2020-11-22 | Add documentation, fix tiny privdrop bug | Laurent Bercot | |
 |
index : s6-networking | |
| Mirror of git://git.skarnet.org/s6-networking |
| summaryrefslogtreecommitdiff |