How can we update the SSL libraries as there are no program updates?

[spudgun]

I've tried manually copying across the 4 latest ssl .dll files, but that doesn't seem to work as you get exception errors in Flash when connecting to SSL enabled sites and also this message doesn't popup when you start the program - Winsock 2.2 -- OpenSSL 1.1.0e 16 Feb 2017 - as after changing to the new .dll files it just says - Winsock 2.2 - so is there a way to do this without there being a program update which looks pretty unlikely at the moment?

[MxxCon]

Make sure that those dll files are 32bit, not 64bit.
Beyond that there's probably not much that can be done. :/

[spudgun]

Make sure that those dll files are 32bit, not 64bit.
Beyond that there's probably not much that can be done. :/

Thanks, I did make sure that I was using the 32bit .dll files - but no joy - so guess this is will become obsolete as soon as requirements are in force on host FTP sites for later SSL versions.

Any ideas on other FXP programs that can be used instead?

[dozegfx]

Win32 versions of the below are confirmed working.

libcrypto-1_1.dll and libssl-1_1.dll 1.1.0i work. (latest working, doesn't work with 1.1.1)

libeay32.dll and ssleay32.dll 1.0.2p work. (latest)

Hope that helps.

[spudgun]

Win32 versions of the below are confirmed working.

libcrypto-1_1.dll and libssl-1_1.dll 1.1.0i work. (latest working, doesn't work with 1.1.1)

libeay32.dll and ssleay32.dll 1.0.2p work. (latest)

Hope that helps.

Thank you very much, that is most helpful

[msg7086]

OpenSSL changes its API between point releases. Make sure you only update to the latest alphabets version.

So (as of now) 1.1.0j should work, but 1.1.1 will probably not.