<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body dir="auto"><div dir="auto">Unless you need to specify an alternative engine I would suggest not trying to manually configure things this way.</div><div dir="auto"><br></div><div dir="auto">Is there a reason you don't want to just use ssl_certificate and ssl_certificate_key?</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div id="composer_signature" dir="auto"><div style="font-size:85%;color:#575757" dir="auto">Sent from my T-Mobile 5G Device</div></div><div dir="auto"><br></div><div><br></div><div align="left" dir="auto" style="font-size:100%;color:#000000"><div>-------- Original message --------</div><div>From: vishwaskn <nginx-forum@forum.nginx.org> </div><div>Date: 7/4/21 17:42 (GMT-05:00) </div><div>To: nginx@nginx.org </div><div>Subject: ssl_engine configuration </div><div><br></div></div>Hello All,<br><br>Could you please point me to a configuration example of using ssl_engine<br>configuration directive ?.<br><br>Is there a patch needed to nginx to get it work as I saw a few discussions<br>around this or are they already merged to mainline ?.<br><br>I see here<br>(http://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_certificate_key)<br>the usage example of using ssl_certifcate_key specifying a engine:name:id,<br>however it is not clear to me, what should be the "id" here.<br>Also, I presume, the ssl_engine is a global directive and should be<br>indicated with the engine name as identified by openssl.<br><br>Any pointers/references regarding getting ssl_engine working with nginx<br>would be helpful.<br><br>thank you,<br>regards,<br>-vishwas.<br><br>Posted at Nginx Forum: https://forum.nginx.org/read.php?2,291983,291983#msg-291983<br><br>_______________________________________________<br>nginx mailing list<br>nginx@nginx.org<br>http://mailman.nginx.org/mailman/listinfo/nginx<br><br></body></html>