| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Prepare for 2.4.2.0; implement client certificates with bearssl | Laurent Bercot | 2021-05-18 | 1 | -2/+4 |
| | | | | | Also send a bit more environment with libtls | ||||
| * | More doc fixes | Laurent Bercot | 2021-02-16 | 1 | -2/+2 |
| | | |||||
| * | More doc fixes | Laurent Bercot | 2021-02-04 | 1 | -2/+2 |
| | | |||||
| * | Remove SSL_TLS_SNI_SERVERNAME (instead of defined but empty) if no SNI | Laurent Bercot | 2021-01-28 | 1 | -5/+3 |
| | | |||||
| * | Prepare for 2.4.1.0; add SSL_TLS_SNI_SERVERNAME | Laurent Bercot | 2021-01-28 | 1 | -2/+5 |
| | | |||||
| * | Implement handshake timeout for libtls backend | Laurent Bercot | 2021-01-13 | 1 | -3/+1 |
| | | |||||
| * | Change -K semantics: timeout *during handshake*, not afterwards | Laurent Bercot | 2020-12-07 | 1 | -4/+6 |
| | | | | | | | | | | | | | | | - 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. | ||||
| * | Add documentation, fix tiny privdrop bug | Laurent Bercot | 2020-11-22 | 1 | -0/+212 |
 |
index : s6-networking | |
| UCSPI TCP implementation and other networking utilities | ska-skaware@skarnet.org |
| aboutsummaryrefslogtreecommitdiffstats |