On 17/10/2018 18:59, Black Michael via wsjt-devel wrote:
I copied the most current libeay32.dll into the wsjtx bin directory
but that doesn't solve the problem.
Instead just needed ssleay32.dll in there and it works OK now.
Hi Mike,
you need both DLLs.
Most of those OpenSSL libs in other packages are packaged illegally, the
US prohibits export of strong cryptography without signing a special
agreement with them. Even then exporting to Iran, DRPK etc. is prohibited.
I will get the others to try installing a recent official OpenSSL
package and check that it fixes it for them. One further problem is that
although putting the DLLs in the WSJT-X bin directory will certainly
mean they get used, that will also interfere with the uninstaller which
will not be allowed to delete them and therefore cannot clean up the
install directories. OTOH putting the OpenSSL DLLs on PATH will
potentially break other applications - DLL Hell in its worst form.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
