<feed xmlns='http://www.w3.org/2005/Atom'>
<title>s6-networking/src/stls, branch v2.4.0.0</title>
<subtitle>UCSPI TCP implementation and other networking utilities</subtitle>
<id>http://git.skarnet.org/cgit/s6-networking/atom/src/stls?h=v2.4.0.0</id>
<link rel='self' href='http://git.skarnet.org/cgit/s6-networking/atom/src/stls?h=v2.4.0.0'/>
<link rel='alternate' type='text/html' href='http://git.skarnet.org/cgit/s6-networking/'/>
<updated>2020-12-07T12:53:54Z</updated>
<entry>
<title> Change -K semantics: timeout *during handshake*, not afterwards</title>
<updated>2020-12-07T12:53:54Z</updated>
<author>
<name>Laurent Bercot</name>
<email>ska-skaware@skarnet.org</email>
</author>
<published>2020-12-07T12:53:54Z</published>
<link rel='alternate' type='text/html' href='http://git.skarnet.org/cgit/s6-networking/commit/?id=f7e676abdc799fcee5138807447b5e91ab05508f'/>
<id>urn:sha1:f7e676abdc799fcee5138807447b5e91ab05508f</id>
<content type='text'>
 - 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.
</content>
</entry>
<entry>
<title> stls client: prefer CAFILE, warn on CADIR use, because libtls is broken</title>
<updated>2020-11-23T15:39:17Z</updated>
<author>
<name>Laurent Bercot</name>
<email>ska-skaware@skarnet.org</email>
</author>
<published>2020-11-23T15:39:17Z</published>
<link rel='alternate' type='text/html' href='http://git.skarnet.org/cgit/s6-networking/commit/?id=030ba53485e9b8a2793e1f1c9c8f62f8b8987e95'/>
<id>urn:sha1:030ba53485e9b8a2793e1f1c9c8f62f8b8987e95</id>
<content type='text'>
</content>
</entry>
<entry>
<title> Fix more bugs; disable renegociation in bearssl client</title>
<updated>2020-11-23T14:25:24Z</updated>
<author>
<name>Laurent Bercot</name>
<email>ska-skaware@skarnet.org</email>
</author>
<published>2020-11-23T14:25:24Z</published>
<link rel='alternate' type='text/html' href='http://git.skarnet.org/cgit/s6-networking/commit/?id=564631637bcd238b4c9aad5496aa9e049f948dd9'/>
<id>urn:sha1:564631637bcd238b4c9aad5496aa9e049f948dd9</id>
<content type='text'>
</content>
</entry>
<entry>
<title> Fix a few bugs. sbearssl appears to be working.</title>
<updated>2020-11-22T21:49:58Z</updated>
<author>
<name>Laurent Bercot</name>
<email>ska-skaware@skarnet.org</email>
</author>
<published>2020-11-22T21:49:58Z</published>
<link rel='alternate' type='text/html' href='http://git.skarnet.org/cgit/s6-networking/commit/?id=bae11b88357db72b19413cd05c62ac9242b9b597'/>
<id>urn:sha1:bae11b88357db72b19413cd05c62ac9242b9b597</id>
<content type='text'>
</content>
</entry>
<entry>
<title> Add SSL_PROTOCOL and SSL_CIPHER support, fix some bugs</title>
<updated>2020-11-22T15:46:34Z</updated>
<author>
<name>Laurent Bercot</name>
<email>ska-skaware@skarnet.org</email>
</author>
<published>2020-11-22T15:46:34Z</published>
<link rel='alternate' type='text/html' href='http://git.skarnet.org/cgit/s6-networking/commit/?id=4fb917263ac30373cb3e5dfe3e207369eb238def'/>
<id>urn:sha1:4fb917263ac30373cb3e5dfe3e207369eb238def</id>
<content type='text'>
</content>
</entry>
<entry>
<title> Add documentation, fix tiny privdrop bug</title>
<updated>2020-11-22T00:16:06Z</updated>
<author>
<name>Laurent Bercot</name>
<email>ska-skaware@skarnet.org</email>
</author>
<published>2020-11-22T00:16:06Z</published>
<link rel='alternate' type='text/html' href='http://git.skarnet.org/cgit/s6-networking/commit/?id=47cbbb1619ace4013856843ef8f7d68279c74faa'/>
<id>urn:sha1:47cbbb1619ace4013856843ef8f7d68279c74faa</id>
<content type='text'>
</content>
</entry>
<entry>
<title> Privs can only be dropped after reading key files.</title>
<updated>2020-11-21T02:22:09Z</updated>
<author>
<name>Laurent Bercot</name>
<email>ska-skaware@skarnet.org</email>
</author>
<published>2020-11-21T02:22:09Z</published>
<link rel='alternate' type='text/html' href='http://git.skarnet.org/cgit/s6-networking/commit/?id=5c2880becc94141b8035b3488b6bd60696011308'/>
<id>urn:sha1:5c2880becc94141b8035b3488b6bd60696011308</id>
<content type='text'>
</content>
</entry>
<entry>
<title> Refactor tls code to support ucspi-tls</title>
<updated>2020-11-20T23:24:29Z</updated>
<author>
<name>Laurent Bercot</name>
<email>ska-skaware@skarnet.org</email>
</author>
<published>2020-11-20T23:24:29Z</published>
<link rel='alternate' type='text/html' href='http://git.skarnet.org/cgit/s6-networking/commit/?id=5715c21a077ee1c2fe8957cb4adcea14fd2eda6b'/>
<id>urn:sha1:5715c21a077ee1c2fe8957cb4adcea14fd2eda6b</id>
<content type='text'>
 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.
</content>
</entry>
<entry>
<title> Moderately big hammer: force kill on s6-tlsd when it has nothing to write to the network</title>
<updated>2017-08-28T21:10:03Z</updated>
<author>
<name>Laurent Bercot</name>
<email>ska-skaware@skarnet.org</email>
</author>
<published>2017-08-28T21:10:03Z</published>
<link rel='alternate' type='text/html' href='http://git.skarnet.org/cgit/s6-networking/commit/?id=5691bc64df8444cfbebe7a97480f49f79497b19b'/>
<id>urn:sha1:5691bc64df8444cfbebe7a97480f49f79497b19b</id>
<content type='text'>
</content>
</entry>
<entry>
<title> Revert big hammer. Data still needs to be flushed to the network even when the local app dies.</title>
<updated>2017-08-28T20:30:00Z</updated>
<author>
<name>Laurent Bercot</name>
<email>ska-skaware@skarnet.org</email>
</author>
<published>2017-08-28T20:30:00Z</published>
<link rel='alternate' type='text/html' href='http://git.skarnet.org/cgit/s6-networking/commit/?id=d594db1b68d6a2c890d385087799dd8cdf6dc966'/>
<id>urn:sha1:d594db1b68d6a2c890d385087799dd8cdf6dc966</id>
<content type='text'>
</content>
</entry>
</feed>
