I'm not a big fan of OpenSSL.
How tight is OpenSSL integrated into vibe?
Is it possible to replace it or extend vibe to use different SSL backende?
What parts does vibe need at all?
Maybe just doing these is enough as we don't need a full blown OpenSSL.
Robert M. Münch
http://www.saphirion.com
smarter | better | faster
Am 16.01.2016 um 12:24 schrieb Robert M. Münch:
I'm not a big fan of OpenSSL.
How tight is OpenSSL integrated into vibe?
Is it possible to replace it or extend vibe to use different SSL backende?
What parts does vibe need at all?Maybe just doing these is enough as we don't need a full blown OpenSSL.
There is currently the possibility to use the Botan D port [1] instead
of OpenSSL, but any other implementation is possible by implementing the TLSContext and TLSStream interfaces.
Botan currently still has build issues on Windows when using Optlink, so
it isn't used by default. But it will be enabled automatically if you
fetch the package (dub fetch botan). You can then disable the OpenSSL
dependency by defining "versions": ["VibeNoSSL"] (resp. versions <br>"VibeNoSSL" in dub.sdl).
