René Meusel

@randombit This is now based on #3010 and #3011. Note that I integrated the changes in my self-review into the respective commits.

Rebased to master to pick up the emscripten fix.

Rebased to master to pick up the emscripten fix.

Mhh, unfortunatly, i cannot reproduce this trivially. The assertion is inside `std::vector` in the STL: Basically complaining about an out-of-bounds access to `std::vector::operator[]`. A stack trace of this would be...

Rebased and retargeted to master.

Rebased to master.

Rebased and retargeted to master.

Apparently the build scripts failed to find visual studio's `nmake` utility: ``` FAILED: botan-prefix/src/botan-stamp/botan-build cmd.exe /C "cd /D C:.hunter_Base\8a34475\e755729\cea224c\Build\botan\Source && nmake -j 32 libs && C:\Qt\Tools\CMake_64\bin\cmake.exe -E touch C:/.hunter/_Base/8a34475/e755729/cea224c/Build/botan/Build/botan-prefix/src/botan-stamp/botan-build" 'nmake'...

You have a few options: 1. Override `Credentials_Manager::trusted_certificate_authorities()` and return a `Certificate_Store` (e.g. `Certificate_Store_In_Memory`) that exclusively contains your desired CA. 2. Override `TLS::Callbacks::tls_verify_cert_chain()` which is called by the TLS implementation...

What you are trying to implement is a hybrid encryption scheme. Because RSA on its own cannot encrypt arbitrarily large data streams. In short you should: encrypt/authenticate your payload data...