>> Currently, I?ve coded it so that this only happens when the client does not >> specify an SNI, but I?m looking for guidance on what you would consider to be >> the best solution. This approach can certainly be taken to be compatible with >> SNI. >> >> Is this something that you would be interested in folding into the codebase? > > Well, you explained what it does but not the purpose. In what does this > constitute an improvement, for what use case ? Does it fix a connection > trouble for some clients, or does it improve security and/or performance ? > > I must say I don't really understand the purpose. Maybe you and/or Olivier > who would like this as well and/or anyone else could put some insights here ?
Currently we mostly use RSA certificates. ECC (ECDSA) are different certificates and until RSA certificates are fully removed from the industry, we will have to support both. The change, if I understand correctly, allows serving the ECC/ECDSA certificate when the client supports it (via ciphers list), and RSA otherwise. Do we need this? Absolutely yes. But we will have to verify exactly whats the best way to do this, and how openssl can help with this. I believe openssl 1.0.2 introduces a new API which makes things simpler. Apache 2.4 can already do this, nginx not yet. Some discussions and further informations: https://github.com/igrigorik/istlsfastyet.com/issues/38 http://mailman.nginx.org/pipermail/nginx-devel/2013-October/004376.html https://blog.cloudflare.com/ecdsa-the-digital-signature-algorithm-of-a-better-internet/ https://blog.joelj.org/2015/06/19/dual-rsaecdsa-certificates-in-apache-2-4/ https://securitypitfalls.wordpress.com/2014/10/06/rsa-and-ecdsa-performance/ Regards, Lukas
