Recent

Author Topic: Could not initialize openSSL library ? [SOLVED]  (Read 12107 times)

Robert W.B.

  • Sr. Member
  • ****
  • Posts: 328
  • Love my Wife, My Kids and Lazarus/Freepascal.
Could not initialize openSSL library ? [SOLVED]
« on: May 28, 2018, 12:58:01 pm »
Hi friends.
I have developed a complete Lazarus app and now i want to distribute it as a demo to my users.
I usually use windows urlmon to download data from the server but, now i use fphttpclient instead, when i download data from the server.
My hopes is that fphttpclient will work on Mac also.
From Lazarus client, the app works fine but, when i use fphttpclient in my Lazarus app on a computer without Lasarus i get this error:Could not initialize openSSL library ?

Is there anyone who can answer which openSSL library, which is compatible with my Lazarus app, I have to use when I will distribute the app.

Thanks in advance.
Bob
« Last Edit: May 29, 2018, 01:25:10 am by R.Blennerhed »
Rob

Phil

  • Hero Member
  • *****
  • Posts: 2737
Re: Could not initialize openSSL library ?
« Reply #1 on: May 28, 2018, 03:02:25 pm »
Is there anyone who can answer which openSSL library, which is compatible with my Lazarus app, I have to use when I will distribute the app.

On Windows, you'll need to include ssleay32.dll and libeay32.dll from here:

http://indy.fulgan.com/SSL/

Make sure you have the right bitness (32-bit / 64-bit). They're named the same.


Thaddy

  • Hero Member
  • *****
  • Posts: 14205
  • Probably until I exterminate Putin.
Re: Could not initialize openSSL library ?
« Reply #2 on: May 28, 2018, 03:37:19 pm »
Is there anyone who can answer which openSSL library, which is compatible with my Lazarus app, I have to use when I will distribute the app.

On Windows, you'll need to include ssleay32.dll and libeay32.dll from here:

http://indy.fulgan.com/SSL/

Make sure you have the right bitness (32-bit / 64-bit). They're named the same.
On a MAC openssl is phased out? I forgot what replaced it. My Mac is lazy.
Specialize a type, not a var.

Phil

  • Hero Member
  • *****
  • Posts: 2737
Re: Could not initialize openSSL library ?
« Reply #3 on: May 28, 2018, 03:46:13 pm »
On a MAC openssl is phased out? I forgot what replaced it. My Mac is lazy.

Why are you shouting?

On Mac, they're still there, although deprecated for years:

https://developer.apple.com/library/content/documentation/Security/Conceptual/cryptoservices/SecureNetworkCommunicationAPIs/SecureNetworkCommunicationAPIs.html#//apple_ref/doc/uid/TP40011172-CH13-SW3

fphttpclient should work fine on Mac too.

Thaddy

  • Hero Member
  • *****
  • Posts: 14205
  • Probably until I exterminate Putin.
Re: Could not initialize openSSL library ?
« Reply #4 on: May 28, 2018, 05:08:10 pm »
I is not shouting - at least did not mean to -, but current, and it does not work anymore unless you have a 32 bit mac.
Specialize a type, not a var.

Phil

  • Hero Member
  • *****
  • Posts: 2737
Re: Could not initialize openSSL library ?
« Reply #5 on: May 28, 2018, 05:11:13 pm »
I is not shouting - at least did not mean to -, but current, and it does not work anymore unless you have a 32 bit mac.

No, works fine. They're universal libs with both 32-bit and 64-bit architectures.


Remy Lebeau

  • Hero Member
  • *****
  • Posts: 1312
    • Lebeau Software
Re: Could not initialize openSSL library ?
« Reply #6 on: May 30, 2018, 06:56:15 pm »
On Windows, you'll need to include ssleay32.dll and libeay32.dll from here:

http://indy.fulgan.com/SSL/

Note: those DLLs are primarily meant for use with Indy, which FPHttpClient does not use.  Any OpenSSL distribution should work fine.  The only real difference between Indy's distribution and other 3rd party distributions is that the DLLs in Indy's distribution have no external dependencies, such as to Microsoft's VC++ runtime.  Other distributions may, so be mindful of that.
Remy Lebeau
Lebeau Software - Owner, Developer
Internet Direct (Indy) - Admin, Developer (Support forum)

 

TinyPortal © 2005-2018