We have an application running on Windows 8.1 (HP) tablets that is mostly statically linked except for a few libraries, including the SSLEAY32 and LIBEAY32 libraries.
We're using version 1.0.2 of the OpenSSL libraries. We ship our executable and these two libraries and then set a PATH entry in the registry that points to our 'lib' directory so the system/library loader can find the libraries at load/run time. There are two other packages on these tablets we ship that include older versions of the OpenSSL libraries - Intel TXE Components/TCS (OpenSSL version 1.0.0g) and HP Registration service (1.0.0d). Works well. Until the user runs Windows updates.... Then, when our application starts we get a 'The ordinal 3905 could not be located in the dynamic link library 'C:\program Files\<our installdir>\lib\SSALEAY32.dll'. I've tried the following - all to no avail: removing the HP and Intel OpenSSL libraries (but safe-keeping them for later re-installation) Re-installing our application and OpenSSL libraries Interestingly, the OpenSSL libraries in the HP and Intel installations do not change after the Windows update - they're the same versions as before the update.... I'm stumped. Any clues? I'm guessing the best course of action is to statically link the OpenSSL libs into our app. Is that a good plan? Thanks for the help. Russ Loucks ---- Russ Loucks mailto: r...@mnmicro.net Winter is coming
-- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
