SSL handshake error

[Remy Lebeau]

Does it mean that Indy will load libleay32.dll and ssleay32.dll dynamically?

Yes, it does.

Does it load the dll with a specific search path?

By default, no.  It relies on the OS's standard search path.  However, Indy has an IdOpenSSLSetLibPath() function in the IdSSLOpenSSLHeaders unit which you can call at runtime if you want to specify a specific folder where Indy will load the DLLs from.

I need to create a portable program that runs from a flash drive. Would it be enough to copy the good OpenSSL DLL Files in the same directory, or do I need to do something specific to load those exact DLL files?

You should put the DLLs in the same folder as your EXE, that is the first place the OS looks by default.

[Remy Lebeau]

You can put them in the same directory as the application, or a sub directory

Yes, that is best.  Or in any other folder that your app has control over.

I would recommend to build in a check if in the official windows directories for libraries a version is already available and if not put them there..

Unlike other platforms, Windows does not ship with OpenSSL pre-installed.  And manually putting OpenSSL libraries (or any third-party libraries, for that matter) into the system folders would be a big mistake.  Microsoft really discourages that.