<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Yes, the s_client and s_server core is …<div>There are even bugs filled <a href="https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/396818">https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/396818</a></div><div><br></div><div>But this is different. The SSL_CTX_set_default_verify_paths does not have a bug, </div><div>but the usage of it is wrong.</div><div><br></div><div>Cheers.</div><div><br></div><div><br><div><div>On 11 Sep 2014, at 05:14, Philipp <<a href="mailto:e1c1bac6253dc54a1e89ddc046585792@posteo.net">e1c1bac6253dc54a1e89ddc046585792@posteo.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Am 11.09.2014 00:56 schrieb Michal Cichra:<br><blockquote type="cite">What I propose is a configuration flag, to set<br>`SSL_CTX_set_default_verify_paths`.<br></blockquote><br>Careful what you wish for..<br><br>I didnt check the surrounding code, but above call and CAfile/CApath sets (if cmd-line or via API wont matter)<br>has "funny" error conditions; see this post and the thread:<br><a href="http://marc.info/?l=openbsd-tech&m=140646297120492&w=2">http://marc.info/?l=openbsd-tech&m=140646297120492&w=2</a><br><br>Just a 2ct heads up.<br><br>_______________________________________________<br>nginx mailing list<br>nginx@nginx.org<br>http://mailman.nginx.org/mailman/listinfo/nginx<br></blockquote></div><br></div></body></html>