<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Hello,</div><div class=""><br class=""></div><div class="">I have a question.</div><div class=""><br class=""></div><div class="">I have the following TLS scenarios:</div><div class=""><br class=""></div><div class="">1) A local user for a domain I own, connects to my server using TLS. If the domain is local, I will authenticate the user against my database and I do not care if the user has a certificate</div><div class="">2) A remote server, connects to my server using TLS and pretends that is <a href="http://domainX.com" class="">domainX.com</a>. In such case, the only way to verify that this is true is by requiring a certificate and verify it</div><div class=""><br class=""></div><div class="">So there is a logic split between when to require and how to verify a certificate depending on the fact that we deal with a local user or a foreign domain.</div><div class=""><br class=""></div><div class="">I would like to know if is possible to set <span style="font-family: Helvetica, Arial; text-align: justify; background-color: rgb(255, 255, 255);" class="">require_cert and </span><span style="font-family: Helvetica, Arial; text-align: justify; background-color: rgb(255, 255, 255);" class="">verify_cert on the fly, while routing packets, instead of configuring them statically per domain.</span><div class=""><br class=""></div></div><div class="">Regards,</div><div class="">Adrian</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""> </div></body></html>