Unless you need to specify an alternative engine I would suggest not trying to manually configure things this way.Is there a reason you don't want to just use ssl_certificate and ssl_certificate_key?Sent from my T-Mobile 5G Device
-------- Original message --------From: vishwaskn <nginx-forum@forum.nginx.org> Date: 7/4/21 17:42 (GMT-05:00) To: nginx@nginx.org Subject: ssl_engine configuration Hello All,Could you please point me to a configuration example of using ssl_engineconfiguration directive ?.Is there a patch needed to nginx to get it work as I saw a few discussionsaround this or are they already merged to mainline ?.I see here(http://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_certificate_key)the usage example of using ssl_certifcate_key specifying a engine:name:id,however it is not clear to me, what should be the "id" here.Also, I presume, the ssl_engine is a global directive and should beindicated with the engine name as identified by openssl.Any pointers/references regarding getting ssl_engine working with nginxwould be helpful.thank you,regards,-vishwas.Posted at Nginx Forum: https://forum.nginx.org/read.php?2,291983,291983#msg-291983_______________________________________________nginx mailing listnginx@nginx.orghttp://mailman.nginx.org/mailman/listinfo/nginx_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx