Providers in OPENSSL 3.0 to replace Third Party Engine(OPENSSL 1.0.2)

[Paramashivaiah, Sunil]

Hi All,

         We are migrating our application to use OPENSSL 3.0 from OPENSSL 1.0.2. We have ENGINE related code which loads
a third party lib.so as engine. We are using the below set of deprecated API's  for that.

     ENGINE_load_dynamic(),ENGINE_by_id("dynamic"),ENGINE_ctrl_cmd_string(e, "SO_PATH", lib.c_str(), 0).

     Now in OPENSSL 3.0 as we understand we need to use PROVIDERS to achieve the above functionality.
     We found API  OSSL_PROVIDER_load() to load and initialize the provider.

     Can we use the same lib.so which we were using for ENGINE to replace it as provider  and Please let us know
     how we can use it in  OSSL_PROVIDER_load() API to load a third party lib.so.

Thanks and Regards,
Sunil


Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mta.openssl.org/pipermail/openssl-users/attachments/20211006/a00423b8/attachment-0001.html>