BTW I do see what you mean about the ssleay32 dll ... it loads any Libeay32.dll it can find it seems as i found in the loaded modules.
I found this by testing connecting to an older DB software setup that doesn't require SSL/TLS for the ODBC to work. So the ODBC didn't load anything OpenSSL related.
And because of this, ssleay32.cmrs.dll actually loaded a libeay32.dll from a 3rd party program installed on my system.
I am still looking into the whole manifest XML deal but so far coming up short on that.
So probably, only way for now would be compile the DLLs myself and make sure it looks for a different file names and the code in the files are looking for the different file names also.
And modify the INDY code....
As running out of time
I found this by testing connecting to an older DB software setup that doesn't require SSL/TLS for the ODBC to work. So the ODBC didn't load anything OpenSSL related.
And because of this, ssleay32.cmrs.dll actually loaded a libeay32.dll from a 3rd party program installed on my system.
I am still looking into the whole manifest XML deal but so far coming up short on that.
So probably, only way for now would be compile the DLLs myself and make sure it looks for a different file names and the code in the files are looking for the different file names also.
And modify the INDY code....
As running out of time