s6-networking/src/sbearssl/sbearssl_run.c, branch dev UCSPI TCP implementation and other networking utilities https://git.skarnet.org/cgit/s6-networking/atom/src/sbearssl/sbearssl_run.c?h=dev 2021-05-27T19:14:07Z All good, remove debug instructions 2021-05-27T19:14:07Z Laurent Bercot ska-skaware@skarnet.org 2021-05-27T19:14:07Z urn:sha1:d5ce828c97505e429e0cc87b5e87da4f7d291ad4 Add an x509 engine wrapping minimal. NOT FUNCTIONAL, FOR TESTING. 2021-05-20T10:55:18Z Laurent Bercot ska-skaware@skarnet.org 2021-05-20T10:55:18Z urn:sha1:4aae040b1a8aecddcd0e1e959c77bb262fe6b850 Implement handshake timeout for libtls backend 2021-01-13T11:36:16Z Laurent Bercot ska-skaware@skarnet.org 2021-01-13T11:36:16Z urn:sha1:cc7dccb1858e73176814c3a8457ff6f94ff45662 Change -K semantics: timeout *during handshake*, not afterwards 2020-12-07T12:53:54Z Laurent Bercot ska-skaware@skarnet.org 2020-12-07T12:53:54Z urn:sha1:f7e676abdc799fcee5138807447b5e91ab05508f - 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. Convert to new exec.h syntax 2020-11-26T09:47:02Z Laurent Bercot ska-skaware@skarnet.org 2020-11-26T09:47:02Z urn:sha1:26cd94b2a8f6da396058b6c5d6446e237ec9d78f That exit condition is really hard to get right >.> 2020-11-26T01:37:01Z Laurent Bercot ska-skaware@skarnet.org 2020-11-26T01:37:01Z urn:sha1:51a612c34446e10a086947c410aa206fa978d169 Fix engine exit condition for sbearssl 2020-11-26T00:39:05Z Laurent Bercot ska-skaware@skarnet.org 2020-11-26T00:39:05Z urn:sha1:005fae888243b1a9c51c270a689f08699164ac1d Fix a few bugs. sbearssl appears to be working. 2020-11-22T21:49:58Z Laurent Bercot ska-skaware@skarnet.org 2020-11-22T21:49:58Z urn:sha1:bae11b88357db72b19413cd05c62ac9242b9b597 Refactor tls code to support ucspi-tls 2020-11-20T23:24:29Z Laurent Bercot ska-skaware@skarnet.org 2020-11-20T23:24:29Z urn:sha1:5715c21a077ee1c2fe8957cb4adcea14fd2eda6b That includes: - new architecture: the tls binary is now a child of the app instead of the other way around - the sbearssl_run engine now takes a post-handshake callback. This allows s6-tlsc and s6-tlsd to only exec into the app when the handshake succeeds (which was already the case with libressl). - new binaries s6-tlsc-io and s6-tlsd-io encapsulate the crypto code; they init and run the engine, connecting to 4 already open fds (stdin/stdout = network, argv[1] and argv[2] = local) - s6-tlsc is now a simple wrapper around s6-tlsc-io - s6-tlsd is now a simple wrapper around s6-tlsd-io - new binary: s6-ucspitlsd, which is also a wrapper around s6-tlsd-io, but differently: the parent execs the app which should be ucspi-tls-aware, the child waits for a command from the parent and execs into s6-tlsd-io if it receives it. Moderately big hammer: force kill on s6-tlsd when it has nothing to write to the network 2017-08-28T21:10:03Z Laurent Bercot ska-skaware@skarnet.org 2017-08-28T21:10:03Z urn:sha1:5691bc64df8444cfbebe7a97480f49f79497b19b