Hi,
with recent incarnations, OpenSSL changed DLL names on windows platform - "libssl1_1.dll" and "libcrypto-1_1.dll" instead old libssl32 | libeay32. Here's patch that makes possible to use latest openssl with synapse (svn trunk).
Patch requres "manual" configuration of TTCPBlockSocket.SSL.SSLType in the code because SSL is not supported anymore but I have no elegant sollution to this issue. Maybe to set SslMethodTLSVxx as LT_all?
With so many changing dll/so names, perhaps we should put them in an array rather than numbered variables?
Also i do not think this patch works, it will always load SSLUtilHandle := LoadLib(DLLUtilName2); and discard SSLUtilHandle := LoadLib(DLLUtilName);
Last edit: Benito van der Zander 2018-04-21
And one of the strings has a .dll missing.
Really much better with arrays (attachment). Not sure about the loading order and how to handle version mismatches. Probably should load 1.1, when everything from 1.1 and 1.0 is installed. But when e.g. there is libcrypto 1.1 and 1.0, and libssl 1.0, is it okay to load libcrypto 1.1?
Last edit: Benito van der Zander 2018-04-21
Use ssl_openssl11 plugin instead.
ssl_openssl plugin have limited and not complete support for Openssl 1.1.x. better to use new ssl_opensl11 plugin designed for 1.1.x versions.