FWIW, Wolfgang, I think the easiest way to be sure you have the right DLLs and VS runtime is just to run openssl.exe and see if you get an error message.
The compile process should copy the current version of openssl.exe into your app folder.
Great tip! OpenSSL says, it is missing VCRUNTIME140.dll. This seems to be a Visual C++ Redistributable Package for Visual Studio 2015.https://www.microsoft.com/en-us/download/details.aspx?id=48145
microsoft offers vc_redist.x86.exe and vc_redist.x64.exe. I take both!
I have the x64 version of Windows 10 running on my development machine, but since Clarion programs are still Win32, I suppose I need that one to distribute.
Lets see what happens.....
<a few moments later....>
Ha! That did the trick!
However, I did not need to install that redist-package, because I found it already on my HDD.
I did a
C:\>dir vcruntime140.dll /S /B
and found these two critter:
C:\Program Files (x86)\Mozilla Firefox\vcruntime140.dll
Now I copied the OneDrive one to my EXE-folder, OpenSSL is not complaining and so does my own server. It runs smoothly, as it seems.
I assume, that I have to distribute this VCRUNTIME140.dll now also. Its just 78 kB, it does not hurt.
Thanks you so much, Jane!
Ooops, I was happy too early!
back to digging
I remember that Bruce mentioned to have changed (disabled) some SSL-methods. I think he said this during a webinar. Now to find that one.
Maybe I need to re-issue my own certificate.
This is the very same webserver, made with NT 9: https://126.96.36.199:51443/
That is said about the code-signing algotithm: "PKCS #1 SHA-256 mit RSA-Verschlüsselung"
up-to-date, doesn't it?