Indy and MyDAC needs different SSL dll version

Discussion of open issues, suggestions and bugs regarding MyDAC (Data Access Components for MySQL) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
mysqluser
Posts: 27
Joined: Fri 17 Nov 2006 11:48

Indy and MyDAC needs different SSL dll version

Post by mysqluser » Tue 12 Dec 2006 19:46

hello

now i have a compatiblity problem with the SSL and the LoadLibrary function of MyDAC. I'm using now a component from Indy and they needs a special SSL version of ssleay32.dll and libeay32.dll which MyDAC can't use.

So i think its needed that the developers can set for MyDAC an LoadLibrary folder for this 2 dll files. Can you please add support for it in new MyDAC version, this would be realy realy good. Otherwise i don't know how i now use the normaly dll files for MyDAC and the other two special files for Indy, because as far as i know, Indy also don't supports a LoadLibrary own path.

is there any way that this could be integrated for the next MyDAC version? Or do you have any idea how do i solve this now?

thanks 8)

Antaeus
Posts: 2098
Joined: Tue 14 Feb 2006 10:14

Post by Antaeus » Wed 13 Dec 2006 09:55

We will think about adding possibility to set path to SSL libraries in either of next builds of MyDAC. Meanwhile I can suggest you a solution if you are user of MyDAC Professional version. If you are, send me your license information to Evgeniyd*crlab*com.

gmcsoft
Posts: 2
Joined: Wed 05 Sep 2007 16:52

Post by gmcsoft » Wed 05 Sep 2007 18:00

I have the same problem. But even with the last version where we can set the paths, it doesn't work. Have you got a solution ?

Antaeus
Posts: 2098
Joined: Tue 14 Feb 2006 10:14

Post by Antaeus » Thu 06 Sep 2007 08:34

Now we actively develop our new product, SecureBridge, which helps to ensure security connections in Delphi applications with no external files. Now it supports SSH, and in the nearest time we will add support for SSL. SecureBridge is integrated with MyDAC and Indy.

gmcsoft
Posts: 2
Joined: Wed 05 Sep 2007 16:52

Post by gmcsoft » Thu 06 Sep 2007 08:47

After several hours of testing the many options of LoadLibraryEx, I understood windows cannot handle to have 2 dll loaded with the same file name and the same ressource dll name in one application.

The solution I found is to change the dll names of the openssl dll for indy (version 0.9.6) to (for exemple) 'libeay33.dll' and 'ssleay33.dll'.
I have also modified the dll ressource name which is in the dll. You can do that with an HexEditor. After these modifications, you have to re-compile the IdSSLOpenSSLHeaders.pas (for delphi) with a modification where are mentionned the names of the dll modified.

It is working perfectly .. for those who wants more details about the modification process, you can e-mail me at [email protected]

Post Reply