Re: [Cfrg] Curve manipulation, revisited

[Rob Stradling <[e-mail]>]

On 29/12/14 21:15, Salz, Rich wrote:
>> Some TLS server software (notably Apache httpd) can already use several
>> certs for the same hostname, where each cert has a different public key
>> algorithm (RSA, DSA, ECC).  This means that certs with P-256 and P-384 public
>> keys can be used where there is browser support, with fallback to certs with
>> RSA public keys for the long tail of non-ECC-capable browsers.
>
> Any server that uses OpenSSL can do this, provided they make the calls to register the keypairs.  (And only the NIST curves are currently supported.)

Indeed.

BTW Rich, are the OpenSSL team planning to add support for whatever new 
curve(s) and associated signature algorithm(s) CFRG blesses?

Assuming yes, please will you aim to make it possible for a server to 
register 4 certs/keypairs - RSA, DSA, NIST ECC and CFRG ECC - for the 
same hostname (rather than only permit RSA + DSA + 1 ECC option)?

> So that probably includes, nginx, Node.js, anything built on Ruby or Python, etc.  Some minor code work (config and making an additional API call) could be required, but that's pretty easy.

Nginx can't do this yet, sadly.  I wrote a patch [1], but it's rather 
bitrotten now [2].  Registering the certs/keypairs with OpenSSL was 
indeed "minor code work", but the required updates to the Nginx OCSP 
Stapling code were rather more extensive.  One day I'll find time to 
address the preliminary review comments and finish the job.  :-)


[1] http://osdir.com/ml/nginx-development/2013-10/msg00159.html
[2] http://forum.nginx.org/read.php?2,253440

-- 
Rob Stradling
Senior Research & Development Scientist
COMODO - Creating Trust Online