nginx cannot support provider in openssl3.0

[foxriver1025]

Is there any plan to support the provider mechanism of openssl3.0?

[bibrani-github]

Hi there, You can compiled with openssl3.0.x, you may incorrect on certain parameters

…

________________________________ From: foxriver1025 ***@***.***> Sent: Thursday, June 8, 2023 11:36:17 AM To: intel/asynch_mode_nginx ***@***.***> Cc: Subscribed ***@***.***> Subject: [intel/asynch_mode_nginx] nginx cannot support provider in openssl3.0 (Issue #65) Is there any plan to support the provider mechanism of openssl3.0? — Reply to this email directly, view it on GitHub<#65>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AY5CQ4XGU3VC2B2OAFBX2H3XKFCBPANCNFSM6AAAAAAY6WNF7I>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[foxriver1025]

@bibrani-github Thanks for your reply. I mean can nginx load qatprovider instead of qatengine.
Old versions of OpenSSL supported the ENGINE API. In nginx this is enabled through the ssl_engine directive.
In OpenSSL 3.0 the authors introduced a "Provider API" which is intended to replace the old ENGINE API. It works in a similar way. When using the CLI , I can add -provider qatprovider base to the arguments.
So can this asynch_mode_nginx support qatprovider?

[ShuaiYuan21]

@foxriver1025 Currently, we only support OpenSSL Engine API. We currently have no plans to support the provider API. OpenSSL engine API is still supported in OpenSSL 3.0, even the OpenSSL 1.1.1 will EOL in Sep. 2023. You can still use the Engine API before OpenSSL 4.0, which won't be released until much later. openssl/openssl#20395

[foxriver1025]

@ShuaiYuan21 Thanks. I get it.