UCSPI TCP implementation and other networking utilities https://git.skarnet.org/cgit/s6-networking/atom/.gitignore?h=dev 2020-11-26T00:39:05Z 2020-11-26T00:39:05Z Laurent Bercot ska-skaware@skarnet.org 2020-11-26T00:39:05Z urn:sha1:005fae888243b1a9c51c270a689f08699164ac1d 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. 2018-04-11T15:09:44Z Laurent Bercot ska-skaware@skarnet.org 2018-04-11T15:09:44Z urn:sha1:1e3f94aba1c47b689546ae8ac2e4ba6b1f1774c2 2014-12-15T23:08:59Z Laurent Bercot ska-skaware@skarnet.org 2014-12-15T23:08:59Z urn:sha1:e0fc82203d677a6f1e808e9a1a46176c109d89be