Failed to load SSL DLLS. ssleay32.dll or libeay32.dll/TortoiseSVN

[nj0y]

I found an incompatibility between FlashFXP and TortoiseSVN. TortoiseSVN loads the two SSL DLLs, too, and they remain in memory all the time. When FlashFXP tries to establish an SSL connection, it fails on loading these DLLs (perhaps they have a different version number, I did not check that).

The TortoiseSVN DLLs cannot be unloaded unless you uninstall it, which is not really a solution. So it would be fine if FlashFXP works with the DLLs that are already in memory (that is BTW the meaning of DLLs... to be only loaded once and used multiple times by different processes).

Another FTP program (I do not know if I may mention the name here) uses another DLL: SSL.dll - no idea where it comes from. But this program has no problems with TortoiseSVN.

[Shark]

From memory the FlashFXP dll's had to be modified to allow FFXP to work with them...

I could be wrong, but if thats the case, you will find it hard for these 2 programs to work together.

[bigstar]

FlashFXP requires specific (modified) versions of these dll files, FlashFXP doesn't load them from memory, it loads them from the FlashFXP folder. I don't know what TortoiseSVN is but perhaps it's not compatible with programs that require their own version of these dlls.

[nj0y]

Perhaps it would be a good idea to rename the DLLs when you modified them to avoid conflicts with other software.

TortoiseSVN is a revision control system that permanently resists in memory as it integrates to the Windows Explorer.

Yes, I've had to change FTP clients, as FlashFXP ran into problems with both TortoiseSVN and PHP's OpenSSL extension.

Surely if the 2 dlls are modified, and break compatibility they should have been renamed?

[bigstar]

The modified DLLs provide extended functionality only, they do not and should not break compatiblity with other applications.

FlashFXP installs it's own modified version into the FlashFXP folder for a reason, unless you added FlashFXP to your search path there shouldnt be any problems.

Normally other applications will find the standard version in your windows folder.

Due to the fast pace of OpenSSL revisions it's common for developers to install a copy into their program folder, they know this version works with their software whereas a new version might cause compatiblity issues.

They dont break compatibility with other applications, it is FlashFXP that breaks. It obviously doesnt not load the "extended" versions of the dlls, but attempts to use the pair already in memory, and fails.

Search Path is..
PATH=C:\WINNT\system32;C:\WINNT;C:\Program Files\PostgreSQL\bin;C:\Program Files\Subversion;C:\Program Files\Microsoft Visual Studio\Common\Tools\WinNT;C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin;C:\Program Files\Microsoft Visual Studio\Common\Tools;C:\Program Files\Microsoft Visual Studio\VC98\bin

From FlashFXP log..

[11:48:20] 234 AUTH SSL successful
[11:48:20] Negotiating SSL/TLS session...
[11:48:20] Error: Failed to load SSL DLLS. ssleay32.dll or libeay32.dll
[11:48:20] Connection failed (Connection closed by client)

--
using listdlls.

C:\>listdlls flashfxp

ListDLLs V2.23 - DLL lister for Win9x/NT
Copyright (C) 1997-2000 Mark Russinovich
http://www.sysinternals.com

------------------------------------------------------------------------------
FlashFXP.exe pid: 876
Command line: "C:\Program Files\FlashFXP\FlashFXP.exe"

Base Size Version Path
0x00400000 0x1b1000 2.00.0000.0000 C:\Program Files\FlashFXP\FlashFXP.exe
0x77f80000 0x7b000 5.00.2195.6685 C:\WINNT\system32\ntdll.dll
0x7c4e0000 0xb9000 5.00.2195.6688 C:\WINNT\system32\kernel32.dll
0x77e10000 0x65000 5.00.2195.6688 C:\WINNT\system32\user32.dll
0x77f40000 0x3c000 5.00.2195.6660 C:\WINNT\system32\GDI32.DLL
0x7c2d0000 0x62000 5.00.2195.6710 C:\WINNT\system32\advapi32.dll
0x77d30000 0x6e000 5.00.2195.6753 C:\WINNT\system32\RPCRT4.DLL
0x779b0000 0x9b000 2.40.4522.0000 C:\WINNT\system32\oleaut32.dll
0x77a50000 0xec000 5.00.2195.6769 C:\WINNT\system32\ole32.dll
0x77820000 0x7000 5.00.2195.6623 C:\WINNT\system32\version.dll
0x759b0000 0x6000 5.00.2195.6611 C:\WINNT\system32\LZ32.DLL
0x71710000 0x84000 5.81.4916.0400 C:\WINNT\system32\comctl32.dll
0x77800000 0x1e000 5.00.2195.6659 C:\WINNT\system32\winspool.drv
0x76620000 0x11000 5.00.2195.6611 C:\WINNT\system32\MPR.DLL
0x76b30000 0x3e000 5.00.3700.6693 C:\WINNT\system32\comdlg32.dll
0x70bd0000 0x65000 6.00.2800.1106 C:\WINNT\system32\SHLWAPI.DLL
0x78000000 0x45000 6.01.9844.0000 C:\WINNT\system32\msvcrt.dll
0x782f0000 0x248000 5.00.3700.6705 C:\WINNT\system32\SHELL32.DLL
0x75050000 0x8000 5.00.2195.6603 C:\WINNT\system32\wsock32.dll
0x75030000 0x14000 5.00.2195.6601 C:\WINNT\system32\WS2_32.DLL
0x75020000 0x8000 5.00.2134.0001 C:\WINNT\system32\WS2HELP.DLL
0x77570000 0x30000 5.00.2161.0001 C:\WINNT\system32\winmm.dll
0x75e60000 0x1a000 5.00.2195.6655 C:\WINNT\system32\IMM32.DLL
0x6e420000 0x6000 5.00.2920.0000 C:\WINNT\system32\INDICDLL.dll
0x61210000 0x9000 4.00.0657.0000 C:\Program Files\Microsoft Hardware\Mouse\POINT32.dll
0x775a0000 0x86000 2000.02.3504.0000 C:\WINNT\system32\CLBCATQ.DLL
0x77840000 0x3e000 5.00.2195.6705 C:\WINNT\system32\cscui.dll
0x770c0000 0x23000 5.00.2195.6713 C:\WINNT\system32\CSCDLL.DLL
0x10000000 0x9c000 C:\Program Files\TortoiseSVN\tortoisesvn.dll
0x70200000 0x95000 6.00.2800.1106 C:\WINNT\system32\WININET.dll
0x77440000 0x78000 5.131.2195.6661 C:\WINNT\system32\CRYPT32.dll
0x77430000 0x10000 5.00.2195.6666 C:\WINNT\system32\MSASN1.DLL
0x01190000 0xc6000 C:\Program Files\TortoiseSVN\LIBEAY32.dll
0x7c340000 0x56000 7.10.3052.0004 C:\Program Files\TortoiseSVN\MSVCR71.dll
0x01260000 0x26000 C:\Program Files\TortoiseSVN\SSLEAY32.dll
0x13000000 0x77000 4.00.0000.0014 C:\Program Files\TortoiseSVN\libdb40.dll
0x7c3a0000 0x7b000 7.10.3077.0000 C:\Program Files\TortoiseSVN\MSVCP71.dll
0x719b0000 0x8000 6.00.2800.1106 C:\WINNT\system32\SHFOLDER.dll
0x5d300000 0x80000 5.02.3735.0001 C:\WINNT\System32\hhctrl.ocx
0x61220000 0xb000 4.00.0657.0000 C:\Program Files\Microsoft Hardware\Mouse\MSH_ZWF.dll
0x76fa0000 0xf000 5.00.2134.0001 C:\WINNT\system32\ntshrui.dll
0x773e0000 0x15000 3.00.9435.0000 C:\WINNT\system32\ATL.DLL
0x75170000 0x4f000 5.00.2195.6601 C:\WINNT\system32\NETAPI32.DLL
0x01370000 0xf000 5.00.2195.6695 C:\WINNT\system32\SECUR32.DLL
0x751c0000 0x6000 5.00.2134.0001 C:\WINNT\system32\NETRAP.DLL
0x75150000 0xf000 5.00.2195.6666 C:\WINNT\system32\SAMLIB.DLL
0x77950000 0x2a000 5.00.2195.6666 C:\WINNT\system32\WLDAP32.DLL
0x77980000 0x24000 5.00.2195.6680 C:\WINNT\system32\DNSAPI.DLL
0x75160000 0xc000 5.00.2195.6601 C:\WINNT\System32\ntlanman.dll
0x75210000 0x15000 5.00.2195.6601 C:\WINNT\System32\NETUI0.DLL
0x751d0000 0x38000 5.00.2134.0001 C:\WINNT\System32\NETUI1.DLL


It can clearly be seen that FlashFXP is NOT using the local versions of the 2 DLLS.

Just tried to force it to load the local dlls via...

Dynamic-Link Library Redirection

sees some progress if add an empty file called "FlashFxp.exe.local" to the application directory..

But then get..

---------------------------
FlashFXP: FlashFXP.exe - Entry Point Not Found
---------------------------
The procedure entry point HMAC_cleanup could not be located in the dynamic link library libeay32.dll.
---------------------------
OK
---------------------------

which i guess is an added entry point in the flashfxp custom versions.

[bigstar]

Ah I see.. Hmmm....

HMAC_cleanup isn't one of the added extended functions.

I'll look into this more closely and get back to you.

[wojo]

I just got bit by this same error with TortoiseSVN installed.

Any solutions? Creating FlashFXP.exe.local didn't help.

[bigstar]

I'm still investigating this issue.

[bmxer]

is there any fixes on this lately ?

[wojo]

Actually, the latest beta clears everything up, in combination with the latest OpenSSL DLLs. I'm running:

FlashFXP v2.2 build 973 [BETA RELEASE]
WinSock 2.0 -- OpenSSL 0.9.7c 30 Sep 2003

and

TortoiseSVN 1.0.0 build 781

[bigstar]

It looks like I forgot about this thread. Sorry about that.

This was resolved in a beta release of v2.2.