OpenSSL library not found no matter what I try...

[ghisler(Author)]

Well, it is described on the plugin download page:
http://www.ghisler.com/plugins.htm#filesys

I'm even linking to the correct archive files with the dlls.

[rdobslaw]

Sorry to reply to an finished thread, but I have exactly the same problem and I've done all the steps described before:
- Windows 7 (64 bit)
- Totalcmd 8.51a
- Installed "vcredist_x64"
- I downloaded the file as you described in your previous post
- I copied the content of ZIP file's bin folder to totalcmd installation folder and subfodler '64'

Any idea? Did I miss something?

[rdobslaw]

I can not send a link to a screenshot of my 64 folder now, because I am a new meber of this board.

Here is the German error message:
OpenSSL-Bibliothek nicht gefunden!
Um SSL-Verbindungen nutzen zu können, laden Sie bitte die OpenSSL-DLLs aus dem Internet herunter und kopieren sie ins Total Commander-Verzeichnis!

[ghisler(Author)]

First make sure that you are in the right Total Commander directory - you may have multiple installations of TC. Use command
cd %commander_path%
in the command line above the buttons F5, F6 etc. and press ENTER.

Then copy ALL the files from the 64-bit curl distribution to the "64" subdir inside the TC directory. Make sure that they do not land in subdirs of the "64" directory!

[rdobslaw]

Thank you for your fast answer!

The Command:
cd %commander_path%
directly jumps to "C:\Program Files\totalcmd" folder.

Those 6 dll files are directly located inside this folder and also inside the subfolder "64". I have no subfolder inside the "64" folder.

I start total commander as admin.

Can I provide you more information?
Is there a way to generate a log file for the DLL loading process?

[sqa_wizard]

There is still an open question:
Do you use TC 8.51a 32-bit or 64-bit?
In other words: Does the TC window title read "Total Commander (x64)" ?

[rdobslaw]

Sorry, this was somehow stupid of me.

I installed "tcm851ax64.exe", but the caption bar of main windows did not display x64. I had an older 32 bit version installed before.
I did not expect a side by side installtion of two versions and I used the old shortcut.

Now I created a ftps connection and it worked. Sorry again for waisting your time. Thanks a lot! I really love your tool!

[murrayd]

I'm posting this into an old thread because I still found it to be a problem.

OpenSSL libraries included in cURL 7.40.0 are quite old (1.0.0o) now, a period of 2 years is a lifetime for security related software.


Having searched for hours, I found somewhat updated OpenSSL x64 libraries that don't have strange dependencies:

Native windows x64 software develop with Mingw-w64
http://www.drangon.org/mingw

Scroll down to mingw-w64 devel libraries (x64) and use the link under download the latest version (currently: 2015-10-30, including OpenSSL 1.0.1p)

Note: this is for x64 only, x86 (i686) doesn’t work for me with respective 32-bit version of TC.

[PatrikNasfors]

First a greeting to Christian Ghisler. Thanks for at great program! I've been using it daily for many years, and I don't think I can live without it

For the moment I study IT security and therefore I would like to use secure FTP (FTPS) from now on and I don't want to use old (insecure) versions, so I really hope I don't have to use another product to accomplish this.

The problem is that I get the same error message as described here (just in Danish). Since I can see references here to download some specific file version, which are now years old, and OpenSSL is now on version 1.0.2g, I would like to hear if someone is running that version and with exactly which "helper files". Which files (and versions of these) shall be in which directory?

I also wonder if it is necessary to install cURL or some files from that, when I just want to run FTP with SSL (FTPS)? The help files in Total Commander doesn't say so.

So far I have tried installing OpenSSL (Win64OpenSSL-1_0_2g.exe) in both /bin subdirectory and Windows directory and copying the files libeay32.dll, ssleay32.dll and libssl32.dll (just to be sure) to "C:\Program Files\Total Commander" and to 64 subdirectory. Total Commander (x64) 8.51a running both normally and as administrator, all in Windows 7 Pro 64-bit.

I also tried starting 32-bit version of TC, but that made no difference.

The post by murrayd today I can't see any point in using, since it refers to an quite old version of OpenSSL, and as I said, no point in using an old insecure version of a secure protocol. Well, it might be better that using no security at all, but anyway, it should be up-to-date

Any current information will be very appreciated!

Thanks,

Patrik Näsfors

[Dalai]

@murrayd & Patrik: It's an issue in OpenSSL 1.0.2g (and probably the latest versions of 1.0.1 line as well). See http://ghisler.ch/board/viewtopic.php?t=43668

Regards
Dalai

[PatrikNasfors]

Thanks Dalai,

Seems like a probable reason. I didn't find that thread when searching, because it is another (much more technical) error message that is discussed there. So thanks for the info.

I wrote there, and lets see if there comes up a quick solution. Otherwise we might stick to the previous version of OpenSSL for a while, or use some other program

/Patrik

[murrayd]

The post by murrayd today I can't see any point in using, since it refers to an quite old version of OpenSSL,

As you are a future professional, I understand you point. I am not a TC user myself (but I recognize it a great software), I just needed to get FTPS working for a normal office worker to get his job done.

So when there are 3 alternatives: 1) using a 2-year-old version, 2) using a 6-month-old version and 3) quit using TC at all - and it's not mission critical - I still go with option 2, based on "less age, less vulnerability".
As the suggested page has a history of builds, I guess it will get updated eventually.

@Dalai: thanks for the info

[ghisler(Author)]

Please use OpenSSL 1.0.2f, it's not that old.
https://indy.fulgan.com/SSL/

[Damel]

I have these files in 32+64bit combined installation directory of TC:

C:\Program Files (x86)\totalcmd\64\libeay32.dll from https://indy.fulgan.com/SSL/openssl-1.0.2f-x64_86-win64.zip
C:\Program Files (x86)\totalcmd\64\ssleay32.dll from https://indy.fulgan.com/SSL/openssl-1.0.2f-x64_86-win64.zip
C:\Program Files (x86)\totalcmd\64\libssh2.dll
C:\Program Files (x86)\totalcmd\64\libssl32.dll
C:\Program Files (x86)\totalcmd\64\zlib1.dll

C:\Program Files (x86)\totalcmd\libeay32.dll from https://indy.fulgan.com/SSL/openssl-1.0.2f-i386-win32.zip
C:\Program Files (x86)\totalcmd\ssleay32.dll from https://indy.fulgan.com/SSL/openssl-1.0.2f-i386-win32.zip
C:\Program Files (x86)\totalcmd\libssh2.dll
C:\Program Files (x86)\totalcmd\libssl32.dll
C:\Program Files (x86)\totalcmd\zlib1.dll

So can I delete the red ones, or have these some function for TC and me?

[sqa_wizard]

So can I delete the red ones, or have these some function for TC and me?

This depends on how you aure using TC:
For FTPS the green ones are sufficient.
For SFTP you need the red ones too.

If you are not sure, just keep them all for future use. They eat not much disk space.