ObjFW  History of src/tls/OFSecureTransportTLSStream.m of 6f0bb25b4ee2fef1

Mbed TLS is never automatically picked as a TLS implementation and
always needs to be manually enabled using --with-tls=mbedtls. file: [1e41cb22bf] check-in: [11b2a17595] user: js, branch: trunk, size: 6919 [annotate] [blame] [check-ins using] [diff]

This allows for a much cleaner solution to avoid the internal read
buffer of e.g. a TLS connection never being processed while waiting for
a delimiter. file: [89fd642a80] check-in: [a61e0594b4] user: js, branch: trunk, size: 6894 [annotate] [blame] [check-ins using] [diff]

While GnuTLS and SecureTransport haven't shown in practice to need this,
this makes it more robust for future changes in those. In theory, both
could return less data on a read than they have buffered, meaning the
delimiter is not found but in the buffered data, which would then make
them have the same issue OpenSSL had with hanging connections (though
there the problem was that the BIO was not processed and never would
without the same change as in this commit). file: [4775886a79] check-in: [1a3613d573] user: js, branch: trunk, size: 7445 [annotate] [blame] [check-ins using] [diff]

These implementations all depend on additional libraries that are
otherwise not needed for an ObjFW application that does not use TLS,
meaning they would add unnecessary dependencies for a lot of
applications and waste memory. file: [ce137cf9dc] check-in: [8f8af474fc] user: js, branch: trunk, size: 6464 [annotate] [blame] [check-ins using] [diff]

This implements OFTLSStream using Apple's Secure Transport. While Secure
Transport is declared deprecated by Apple, Apple so far has failed to
provide a suitable replacement. They recommend Network.framework as a
replacement, however it can neither work on arbitrary sockets, nor can
it do STARTTLS. file: [56d8fa21c4] check-in: [112eb62f7b] user: js, branch: trunk, size: 6156 [annotate] [blame] [check-ins using]