René Meusel

Closing, as all the integrated branches are now merged.

> With https://github.com/randombit/botan/pull/3032 merged I think this needs to be rebased Done! I don't have my yubikey in reach, will sign and re-push once I'm home.

FWIW: The TLS 1.3 implementation (currently under active development) does implement coalescing of handshake messages into single records: https://github.com/randombit/botan/blob/ffe1c30395ed2c6f8d7c89e024185f1c7513b46f/src/lib/tls/tls13/tls_channel_impl_13.h#L26-L66

Rebased onto https://github.com/randombit/botan/pull/3058 and added the code locations to the XML report. Hence. we should first review/merge the code locations and then rebase this again onto master. Edit: *done*

Indeed there's no show stopper. The JUnit reports just won't be used as is. But we certainly can come back to that later.

Rebased to master. This will certainly need another look and compatibility testing round. Maybe it could even be used as a vehicle to find a better alternative to the `tls_dh_agree()`...

Closing as superseded by: https://github.com/randombit/botan/pull/3609

I incoporated the changes and fixes I needed here: https://github.com/Rohde-Schwarz/botan/pull/10 . Mainly, the addition of `./botan-test --report-properties=key:value,other_key:other_value` to set additional properties in `ci_build.py` that can later be used when generating...

Botan 3.0 is now released with support for TLS 1.3: https://github.com/randombit/botan/issues/3209#issuecomment-1503171315

Adding to the 3.0 milestone to keep a tap on this. Might slip to 3.1, though.