Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

No support of OpenSSL 3.x Provider Support in NGINX, OpenSSL Engine API deprecated#787

hardikpatel9 started this conversation inIdeas
Discussion options

We are currently unable to use OpenSSL 3.x providers with NGINX. Since the OpenSSL Engine API is deprecated, we require support for the newer provider interface. Specifically, we are looking for functionality similar to ssl_engine, which allows configuration to be passed via nginx.conf. However, there is currently no mechanism to pass custom provider-specific data through a directory or configuration block.

We are working on(async_mode_nginx) to support different application likeqatengine which now relies engine using the Engine ctrl API as interface between engine and application for set and get params, looking for similar framework support for the provider.

What are the plans for NGINX to support the OpenSSL 3.x "provider" API as a replacement for the deprecated Engine API?

You must be logged in to vote

Replies: 1 comment

Comment options

Nginx supports providers as it normally initializes OpenSSL so you just need to specify and configure the provider in your openssl.cnf. If you use custom OPENSSL_CONF, it might need in some cases also addenv OPENSSL_CONF; to your nginx config but usually even that might not be necessary.

You must be logged in to vote
0 replies
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
Ideas
Labels
None yet
2 participants
@hardikpatel9@bukka

[8]ページ先頭

©2009-2025 Movatter.jp