ObjFW  History of src/OFTLSStream.h of b20446bb3a8a20e6

Mbed TLS is never automatically picked as a TLS implementation and
always needs to be manually enabled using --with-tls=mbedtls. file: [57d0bfe49e] check-in: [11b2a17595] user: js, branch: trunk, size: 5724 [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: [db5ba510f8] check-in: [a61e0594b4] user: js, branch: trunk, size: 5574 [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: [b3a209020a] check-in: [112eb62f7b] user: js, branch: trunk, size: 5359 [annotate] [blame] [check-ins using] [diff]

The previous API could never work cleanly and would always require
hacks, as it needed intercepting all interactions of OFTCPSocket with
the raw socket and did not work at all if the OFTCPSocket had anything
in its read buffer before starting the TLS handshake. This also could
not be fixed easily, as it would have required the object to contain two
read buffers, one for the unencrypted connection and one for the
encrypted connection. There was also no clean way to perform the
handshake in a non-blocking way.

The new API is a lot cleaner and requires none of the hacks, but using
it requires slightly more work. But this is more than made up for by
making a fully asynchronous handshake possible. It uses the concept of a
stream wrapping another stream, meaning the entire connecting part is
being handled by OFTCPSocket and then the connected socket is passed off
to OFTLSStream to wrap it. This also makes for a lot cleaner separation
of concerns. file: [c91283e053] check-in: [d30efa8bbf] user: js, branch: trunk, size: 4764 [annotate] [blame] [check-ins using] [diff]

This should make it easier to add TLS support using various
implementations. file: [38e4f875d1] check-in: [34cb121dc5] user: js, branch: trunk, size: 3479 [annotate] [blame] [check-ins using] [diff]

The current API is too tied to OpenSSL. file: [d519c5a780] check-in: [a5a3047210] user: js, branch: trunk, size: 1142 [annotate] [blame] [check-ins using] [diff]

Instead, explicitly declare them, as OF_ASSUME_NONNULL_{BEGIN,END} does
not apply to implicit return types. This means that after this commit,
all init methods have a nonnull return type, as they should have. file: [19564dc0db] check-in: [2f4e0df8be] user: js, branch: trunk, size: 6010 [annotate] [blame] [check-ins using] [diff]

Only support for storing an invocation, no support for invoking yet. file: [ece0928c2a] check-in: [d6553b4578] user: js, branch: trunk, size: 5996 [annotate] [blame] [check-ins using] [diff]

Casts are now written like types in variable declarations. file: [27187de68b] check-in: [4af49a13c3] user: js, branch: trunk, size: 5955 [annotate] [blame] [check-ins using] [diff]

This changes retaining behavior, meaning properties are not returned
retained and autoreleased anymore, so a property returned from a getter
now needs to be manually retained and autoreleased before calling the
setter. However, this is rarely the case and not using atomic improves
performance. file: [b87af1f574] check-in: [0a73af49f0] user: js, branch: trunk, size: 5940 [annotate] [blame] [check-ins using] [diff]

Forgot to add 2017, even though I already did quite some changes in
2017. file: [979ca5fd2c] check-in: [44f45c2e35] user: js, branch: trunk, size: 5917 [annotate] [blame] [check-ins using] [diff]

While at it, also update the mail address. file: [f7601e6c4d] check-in: [cec0f072f8] user: js, branch: 0.8, size: 7690 [annotate] [blame] [check-ins using] [diff]

While at it, also update the mail address. file: [e9f441720c] check-in: [2a27cf3000] user: js, branch: trunk, size: 7298 [annotate] [blame] [check-ins using] [diff]

Now that we can require GCC >= 4.6, we no longer need to have a category
on OFObject that adds the optional protocol to it. file: [48c2664a3c] check-in: [ba62f00fac] user: js, branch: trunk, size: 7294 [annotate] [blame] [check-ins using] [diff]

This increases the required GCC version from 4.0 to 4.6 (exception:
Apple GCC, which already supports this with >= 4.0 starting with OS X
10.5). Since even GCC 4.6 is really old by now, there is no point in
still supporting something even older and making the code ugly because
of that. While some hardware and OS support was dropped from GCC 4.6
compared to GCC 4.0, there is nothing in there that would be an
interesting target with the exception of BeOS maybe - but a port to BeOS
can also be achieved using the Haiku support. The other dropped OSes are
mostly old versions of OSes while newer ones are still being supported
(and those newer versions of those OSes still support the same
hardware). file: [991f7cbecd] check-in: [48980f2297] user: js, branch: trunk, size: 7335 [annotate] [blame] [check-ins using] [diff]

This is necessary to make GCC (>= 4.6 and Apple GCC) happy as they don't
like the list of property attributes ending in a comma. file: [d1223f2527] check-in: [80e1a9655b] user: js, branch: trunk, size: 7686 [annotate] [blame] [check-ins using] [diff]

Verification is done automatically by default now.

If more complex verification is needed, automatic verification can be
disabled and done manually. file: [59dd8c2542] check-in: [94affb5b29] user: js, branch: trunk, size: 7433 [annotate] [blame] [check-ins using] [diff]

The only places where BOOL is left are those where they are required by
the ABI. file: [dde8b87a0d] check-in: [c5ef582958] user: js, branch: trunk, size: 3301 [annotate] [blame] [check-ins using] [diff]