SSL Nginx 1.11.0 introduces dual ECDSA + RSA SSL certificate support !

eva2000 · May 25, 2016

Nginx 1.11.0 has been released with dual ECDSA + RSA based ssl certificate support meaning nginx can support 2 separate types of ssl certificates - a ECC 256/384 bit ssl certificate or a RSA 2048/3072/4096 bit ssl certificate and automatically serve the most appropriate ssl certificate type to a specific web browser or client connecting to the server.

Shortcut url link to this thread = https://community.centminmod.com/dualsslcerts

Update: Centmin Mod 123.09beta01 and newer versions can fully automate dual ECDSA + RSA SSL certs by setting in persistent config file /etc/centminmod/custom_config.inc the variable, DUALCERTS='y' prior to creating Nginx vhost via centmin.sh menu option 2 or 22 or nv command line.
Code (Text):
DUALCERTS='y'
However, if you want to manually setup dual ECDSA + RSA SSL certs, continue reading below.

Nginx 1.11.0 dual ECDSA + RSA SSL Certificate Setup

Update: November 12, 2016 revisited latest update with Letsencrypt RSA + ECDSA SSL certs

The setup is basically the same as installing a single ssl certificate, just you duplicate the ssl_certificate and ssl_certificate_key lines - one set for normal RSA based SSL certificate which is commonly used and the other set for the ECDSA based ssl certificate. You can see the old discussion of ECC/ECDSA vs RSA based ssl certificates where ECDSA has better performance than RSA but isn't compatible with certain older web browsers on older OSes like WinXP and IE/8 etc.
Code (Text):
  ssl_certificate      /usr/local/nginx/conf/ssl/domain.com/domain.com-acme.cer;
  ssl_certificate      /usr/local/nginx/conf/ssl/domain.com/domain.com-acme-ecc.cer;
  ssl_certificate_key  /usr/local/nginx/conf/ssl/domain.com/domain.com-acme.key;
  ssl_certificate_key  /usr/local/nginx/conf/ssl/domain.com/domain.com-acme-ecc.key;
Nginx 1.11.0 dual ECDSA + RSA SSL Certificate Tests

Tested on latest Centmin Mod 123.09beta01 LEMP stack with Nginx 1.11.0 and using staging test Letsencrypt RSA 2048bit and ECDSA 384bit SSL certificates manually issued and install Centmin Mod 123.09beta01's integration work for Letsencrypt is lagging behind and doesn't support dual ECDSA + RSA ssl certificates right now, so it has to be manually issues and installed. You'd be on your own in the steps for now as what I have done is not suited to production use as on renewal of the ssl certificates it will break down unless I also script it myself for custom renewal of both Letsencrypt ECDSA + RSA ssl certificates - something I may very well do so for Centmin Mod LEMP stack's future Letsencrypt integration work Unfortunately, no free time to do so for now.

nginx -V
nginx version: nginx/1.11.0
built by gcc 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC)
built with OpenSSL 1.0.2h 3 May 2016
TLS SNI support enabled
configure arguments: --with-ld-opt='-ljemalloc -Wl,-z,relro -Wl,-rpath,/usr/local/lib' --with-cc-opt='-m64 -mtune=native -mfpmath=sse -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2' --sbin-path=/usr/local/sbin/nginx --conf-path=/usr/local/nginx/conf/nginx.conf --with-http_stub_status_module --with-http_secure_link_module --with-openssl-opt=enable-tlsext --add-module=../nginx-module-vts --with-libatomic --with-threads --with-http_gzip_static_module --add-dynamic-module=../ngx_brotli --add-dynamic-module=../ngx_pagespeed-release-1.11.33.2-beta --with-http_sub_module --with-http_addition_module --with-http_image_filter_module=dynamic --with-http_geoip_module --with-http_realip_module --add-module=../ngx-fancyindex-0.3.6 --add-module=../ngx_cache_purge-2.3 --add-module=../ngx_devel_kit-0.3.0 --add-dynamic-module=../set-misc-nginx-module-0.30 --add-dynamic-module=../echo-nginx-module-0.59 --add-module=../redis2-nginx-module-0.13 --add-module=../ngx_http_redis-0.3.7 --add-module=../lua-nginx-module-0.10.4 --add-module=../nginx_upstream_check_module-0.3.0 --add-module=../memc-nginx-module-0.17 --add-module=../srcache-nginx-module-0.31 --add-dynamic-module=../headers-more-nginx-module-0.30 --with-http_perl_module=dynamic --with-http_xslt_module=dynamic --with-pcre=../pcre-8.38 --with-pcre-jit --with-http_ssl_module --with-http_v2_module --with-openssl=../openssl-1.0.2h
Click to expand...

Confirming the dual ECDSA + RSA support is working in Nginx 1.11.0, using curl

on CentOS 7.x curl 7.29 supports ECDSA ssl certificates so the connection is served via ECDSA based TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
Code (Text):
curl -Iskv https://domain.com 2>&1 | egrep -A9 'SSL connection using '
* SSL connection using TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
* Server certificate:
*       subject: CN=domain.com
*       start date: May 25 07:23:00 2016 GMT
*       expire date: Aug 23 07:23:00 2016 GMT
*       common name: domain.com
*       issuer: CN=Fake LE Intermediate X1
> HEAD / HTTP/1.1
> User-Agent: curl/7.29.0
> Host: domain.com
on CentOS 6.x, curl 7.19 does not support ECDSA so usually for single ECDSA ssl based web site you will get errors trying to connect via curl 7.19 client tool and the error would look like this
Code (Text):
curl -Iskv https://domain.com                                
* About to connect() to domain.com port 443 (#0)
*   Trying 111.222.333.444... connected
* Connected to domain.com (111.222.333.444) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* warning: ignoring value of ssl.verifyhost
* NSS error -12286
* Closing connection #0
* SSL connect error
real world example of older curl client erroring out is with early wp-cron's connection to ECDSA discussed at Wordpress - wp-cron SSL connect error with Cloudflare SSL ECDSA | Centmin Mod Community Cloudflare free ssl certificates are ECDSA based as well which caused problems with older clients not able to connect to web sites behind Cloudflare's free ECDSA based SSL certificates.

However, with Nginx 1.11.0 dual ECDSA + RSA ssl certificate support, curl 7.19 client now connects via the RSA ssl certificate setup in Nginx and works normally via RSA based TLS_RSA_WITH_AES_128_CBC_SHA connection I have to work on the ssl_cipher preference set though for optimal preferences
Code (Text):
curl -Iskv https://domain.com 2>&1 | egrep -A9 'SSL connection using '
* SSL connection using TLS_RSA_WITH_AES_128_CBC_SHA
* Server certificate:
*       subject: CN=domain.com
*       start date: May 25 12:04:00 2016 GMT
*       expire date: Aug 23 12:04:00 2016 GMT
*       common name: domain.com
*       issuer: CN=Fake LE Intermediate X1
> HEAD / HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.19.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: domain.com
SSLLABS Tests

Using https://dev.ssllabs.com/ssltest/index.html to test browser and clients to see which ssl certificate configuration they connect to depending on what they support

As you can see both ECDSA and RSA based connections are detected and supported in the Nginx 1.11.0 based configuration

eva2000 · May 26, 2016

Did some cipherscan and testssl tests where these tools are compiled against OpenSSL 1.0.2i with chacha20_poly1305 patches so they support both ECDSA and chacha20 and hence why both tests see ECDSA priority first as the clients support it via OpenSSL 1.0.2i

cipherscan run

Code (Text):

cipherscan https://domain.com           
..........................................................................................................................................
Target: domain.com:443

prio  ciphersuite                    protocols              pubkey_size  signature_algoritm       trusted  ticket_hint  ocsp_staple  pfs                 curves                                                                                                                                                curves_ordering
1     ECDHE-ECDSA-CHACHA20-POLY1305  TLSv1.2                384          sha256WithRSAEncryption  False    3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1                                                                                        server
2     ECDHE-ECDSA-AES256-GCM-SHA384  TLSv1.2                384          sha256WithRSAEncryption  False    3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1                                                                                        server
3     ECDHE-ECDSA-AES128-GCM-SHA256  TLSv1.2                384          sha256WithRSAEncryption  False    3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1                                                                                        server
4     ECDHE-ECDSA-AES256-SHA384      TLSv1.2                384          sha256WithRSAEncryption  False    3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1                                                                                        server
5     ECDHE-ECDSA-AES128-SHA256      TLSv1.2                384          sha256WithRSAEncryption  False    3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1                                                                                        server
6     ECDHE-RSA-AES128-GCM-SHA256    TLSv1.2                2048         sha256WithRSAEncryption  False    3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1,brainpoolP256r1,secp256k1,sect571r1,sect571k1,sect409k1,sect409r1,sect283k1,sect283r1  server
7     ECDHE-RSA-AES128-SHA256        TLSv1.2                2048         sha256WithRSAEncryption  False    3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1,brainpoolP256r1,secp256k1,sect571r1,sect571k1,sect409k1,sect409r1,sect283k1,sect283r1  server
8     ECDHE-RSA-AES128-SHA           TLSv1,TLSv1.1,TLSv1.2  2048         sha256WithRSAEncryption  False    3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1,brainpoolP256r1,secp256k1,sect571r1,sect571k1,sect409k1,sect409r1,sect283k1,sect283r1  server
9     ECDHE-ECDSA-AES128-SHA         TLSv1,TLSv1.1,TLSv1.2  384          sha256WithRSAEncryption  False    3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1                                                                                        server
10    AES128-GCM-SHA256              TLSv1.2                2048         sha256WithRSAEncryption  False    3600         False        None                None                                                                                                                                                  server
11    AES128-SHA256                  TLSv1.2                2048         sha256WithRSAEncryption  False    3600         False        None                None                                                                                                                                                  server
12    AES128-SHA                     TLSv1,TLSv1.1,TLSv1.2  2048         sha256WithRSAEncryption  False    3600         False        None                None                                                                                                                                                  server
13    ECDHE-RSA-AES256-GCM-SHA384    TLSv1.2                2048         sha256WithRSAEncryption  False    3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1,brainpoolP256r1,secp256k1,sect571r1,sect571k1,sect409k1,sect409r1,sect283k1,sect283r1  server
14    ECDHE-RSA-AES256-SHA384        TLSv1.2                2048         sha256WithRSAEncryption  False    3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1,brainpoolP256r1,secp256k1,sect571r1,sect571k1,sect409k1,sect409r1,sect283k1,sect283r1  server
15    ECDHE-RSA-AES256-SHA           TLSv1,TLSv1.1,TLSv1.2  2048         sha256WithRSAEncryption  False    3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1,brainpoolP256r1,secp256k1,sect571r1,sect571k1,sect409k1,sect409r1,sect283k1,sect283r1  server
16    ECDHE-ECDSA-AES256-SHA         TLSv1,TLSv1.1,TLSv1.2  384          sha256WithRSAEncryption  False    3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1                                                                                        server
17    AES256-GCM-SHA384              TLSv1.2                2048         sha256WithRSAEncryption  False    3600         False        None                None                                                                                                                                                  server
18    AES256-SHA256                  TLSv1.2                2048         sha256WithRSAEncryption  False    3600         False        None                None                                                                                                                                                  server
19    AES256-SHA                     TLSv1,TLSv1.1,TLSv1.2  2048         sha256WithRSAEncryption  False    3600         False        None                None                                                                                                                                                  server

OCSP stapling: not supported
Cipher ordering: server
Curves ordering: server - fallback: no
Server supports secure renegotiation
Server supported compression methods: NONE
TLS Tolerance: yes

testssl run

Code (Text):

###########################################################
    testssl       2.7dev from https://testssl.sh/dev/
    (1.481 2016/04/21 16:44:56)

      This program is free software. Distribution and
             modification under GPLv2 permitted.
      USAGE w/o ANY WARRANTY. USE IT AT YOUR OWN RISK!

       Please file bugs @ https://testssl.sh/bugs/

###########################################################

Using "OpenSSL 1.0.2-chacha (1.0.2i-dev)" [~183 ciphers]
on 39b087a3fc3c:/usr/local/http2-15/bin/openssl
(built: "reproducible build, date unspecified", platform: "linux-x86_64")


Start 2016-05-25 18:42:59    -->> 111.222.333.444:443 (domain.com) <<--

rDNS (111.222.333.444): domain.com.
Service detected:       HTTP


Testing protocols (via sockets except TLS 1.2, SPDY+HTTP2)

SSLv2      not offered (OK)
SSLv3      not offered (OK)
TLS 1      offered
TLS 1.1    offered
TLS 1.2    offered (OK)
SPDY/NPN   h2, http/1.1 (advertised)
HTTP2/ALPN h2, http/1.1 (offered)

Testing ~standard cipher lists

Null Ciphers                 not offered (OK)
Anonymous NULL Ciphers       not offered (OK)
Anonymous DH Ciphers         not offered (OK)
40 Bit encryption            not offered (OK)
56 Bit encryption            not offered (OK)
Export Ciphers (general)     not offered (OK)
Low (<=64 Bit)               not offered (OK)
DES Ciphers                  not offered (OK)
Medium grade encryption      not offered (OK)
Triple DES Ciphers           not offered (OK)
High grade encryption        offered (OK)


Testing (perfect) forward secrecy, (P)FS -- omitting 3DES, RC4 and Null Encryption here

PFS is offered (OK)  ECDHE-ECDSA-AES256-GCM-SHA384 ECDHE-RSA-AES256-GCM-SHA384 ECDHE-ECDSA-CHACHA20-POLY1305 ECDHE-RSA-CHACHA20-POLY1305 ECDHE-RSA-AES256-SHA384 ECDHE-ECDSA-AES256-SHA384 ECDHE-RSA-AES256-SHA ECDHE-ECDSA-AES256-SHA ECDHE-ECDSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-ECDSA-AES128-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA ECDHE-ECDSA-AES128-SHA


Testing server preferences

Has server cipher order?     yes (OK)
Negotiated protocol          TLSv1.2
Negotiated cipher            ECDHE-ECDSA-CHACHA20-POLY1305, 256 bit ECDH
Cipher order
     TLSv1:     ECDHE-RSA-AES128-SHA ECDHE-ECDSA-AES128-SHA AES128-SHA ECDHE-RSA-AES256-SHA ECDHE-ECDSA-AES256-SHA AES256-SHA
     TLSv1.1:   ECDHE-RSA-AES128-SHA ECDHE-ECDSA-AES128-SHA AES128-SHA ECDHE-RSA-AES256-SHA ECDHE-ECDSA-AES256-SHA AES256-SHA
     TLSv1.2:   ECDHE-ECDSA-CHACHA20-POLY1305 ECDHE-RSA-CHACHA20-POLY1305 ECDHE-ECDSA-AES256-GCM-SHA384 ECDHE-ECDSA-AES128-GCM-SHA256 ECDHE-ECDSA-AES256-SHA384 ECDHE-ECDSA-AES128-SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA ECDHE-ECDSA-AES128-SHA AES128-GCM-SHA256 AES128-SHA256 AES128-SHA ECDHE-RSA-AES256-GCM-SHA384 ECDHE-RSA-AES256-SHA384 ECDHE-RSA-AES256-SHA ECDHE-ECDSA-AES256-SHA AES256-GCM-SHA384 AES256-SHA256 AES256-SHA
     h2:        ECDHE-ECDSA-CHACHA20-POLY1305 AES128-GCM-SHA256 AES128-SHA256 AES128-SHA AES256-GCM-SHA384 AES256-SHA256 AES256-SHA
     http/1.1:  ECDHE-ECDSA-CHACHA20-POLY1305 AES128-GCM-SHA256 AES128-SHA256 AES128-SHA AES256-GCM-SHA384 AES256-SHA256 AES256-SHA


Testing server defaults (Server Hello)

TLS extensions (standard)    "server name/#0" "renegotiation info/#65281" "EC point formats/#11" "session ticket/#35" "heartbeat/#15" "next protocol/#13172"
Session Tickets RFC 5077     3600 seconds (PFS requires session ticket keys to be rotated <= daily)
SSL Session ID support       yes
TLS clock skew               random values, no fingerprinting possible

  Server Certificate #1
   Signature Algorithm          SHA256 with RSA
   Server key size              2048 bits
   Fingerprint / Serial         SHA1 BA7B59F1B2A34AE6807E542CD378855B33507589 / FA5088EC79B17582FCF656D6736D8032EB9B
                                SHA256 300936D1BE03E4FF5EA2DE7267C6A0FBEF9F52BAD47A50EDBA1724ECE857E90F
   Common Name (CN)             "domain.com" (works w/o SNI)
   subjectAltName (SAN)         "domain.com"
   Issuer                       "Fake LE Intermediate X1" ("")
   EV cert (experimental)       no
   Certificate Expiration       89 >= 60 days (2016-05-25 12:04 --> 2016-08-23 12:04 +0000)
   # of certificates provided   2
   Chain of trust (experim.)    "/usr/bin/etc/*.pem" cannot be found / not readable
   Certificate Revocation List  --
   OCSP URI                     http://ocsp.stg-int-x1.letsencrypt.org/
   OCSP stapling                --

  Server Certificate #2
   Signature Algorithm          SHA256 with RSA
   Server key size              384 bits
   Fingerprint / Serial         SHA1 4B3B88028E326B18F3DC43107D6A2F1BB9FB880C / FA3B16C798FD2B69AB155906F1548786B1CA
                                SHA256 A26DFC601BF6308512D199411FB857EAAE9E70DAFF61F1DC17BD234D031A9917
   Common Name (CN)             "domain.com" (works w/o SNI)
   subjectAltName (SAN)         "domain.com"
   Issuer                       "Fake LE Intermediate X1" ("")
   EV cert (experimental)       no
   Certificate Expiration       89 >= 60 days (2016-05-25 12:04 --> 2016-08-23 12:04 +0000)
   # of certificates provided   2
   Chain of trust (experim.)    "/usr/bin/etc/*.pem" cannot be found / not readable
   Certificate Revocation List  --
   OCSP URI                     http://ocsp.stg-int-x1.letsencrypt.org/
   OCSP stapling                --


Testing HTTP header response @ "/"

HTTP Status Code             200 OK
HTTP clock skew              0 sec from localtime
Strict Transport Security    --
Public Key Pinning           --
Server banner                nginx centminmod
Application banner           X-Powered-By: centminmod
Cookie(s)                    (none issued at "/")
Security headers             --
Reverse Proxy banner         --


Testing vulnerabilities

Heartbleed (CVE-2014-0160)                not vulnerable (OK)
CCS (CVE-2014-0224)                       not vulnerable (OK)
Secure Renegotiation (CVE-2009-3555)      not vulnerable (OK)
Secure Client-Initiated Renegotiation     not vulnerable (OK)
CRIME, TLS (CVE-2012-4929)                not vulnerable (OK)
BREACH (CVE-2013-3587)                    no HTTP compression (OK)  - only supplied "/" tested
POODLE, SSL (CVE-2014-3566)               not vulnerable (OK)
TLS_FALLBACK_SCSV (RFC 7507), experim.    Downgrade attack prevention supported (OK)
FREAK (CVE-2015-0204)                     not vulnerable (OK)
DROWN (2016-0800, CVE-2016-0703), exper.  not vulnerable on this port (OK)
                                           make sure you don't use this certificate elsewhere with SSLv2 enabled services
                                           https://censys.io/ipv4?q=A26DFC601BF6308512D199411FB857EAAE9E70DAFF61F1DC17BD234D031A9917 SHA256 300936D1BE03E4FF5EA2DE7267C6A0FBEF9F52BAD47A50EDBA1724ECE857E90F could help you to find out
LOGJAM (CVE-2015-4000), experimental      not vulnerable (OK), common primes not checked. See below for any DH ciphers + bit size
BEAST (CVE-2011-3389)                     TLS1: AES128-SHA AES256-SHA
                                                 ECDHE-ECDSA-AES128-SHA ECDHE-ECDSA-AES256-SHA ECDHE-RSA-AES128-SHA
                                                 ECDHE-RSA-AES256-SHA
                                           VULNERABLE -- but also supports higher protocols (possible mitigation): TLSv1.1 TLSv1.2
RC4 (CVE-2013-2566, CVE-2015-2808)        no RC4 ciphers detected (OK)


Testing all 183 locally available ciphers against the server, ordered by encryption strength

Hexcode  Cipher Suite Name (OpenSSL)    KeyExch.   Encryption Bits
-------------------------------------------------------------------------
xcc14   ECDHE-ECDSA-CHACHA20-POLY1305  ECDH 256   ChaCha20   256       
xcc13   ECDHE-RSA-CHACHA20-POLY1305    ECDH 256   ChaCha20   256       
xc030   ECDHE-RSA-AES256-GCM-SHA384    ECDH 256   AESGCM     256       
xc02c   ECDHE-ECDSA-AES256-GCM-SHA384  ECDH 256   AESGCM     256       
xc028   ECDHE-RSA-AES256-SHA384        ECDH 256   AES        256       
xc024   ECDHE-ECDSA-AES256-SHA384      ECDH 256   AES        256       
xc014   ECDHE-RSA-AES256-SHA           ECDH 256   AES        256       
xc00a   ECDHE-ECDSA-AES256-SHA         ECDH 256   AES        256       
x9d     AES256-GCM-SHA384              RSA        AESGCM     256       
x3d     AES256-SHA256                  RSA        AES        256       
x35     AES256-SHA                     RSA        AES        256       
xc02f   ECDHE-RSA-AES128-GCM-SHA256    ECDH 256   AESGCM     128       
xc02b   ECDHE-ECDSA-AES128-GCM-SHA256  ECDH 256   AESGCM     128       
xc027   ECDHE-RSA-AES128-SHA256        ECDH 256   AES        128       
xc023   ECDHE-ECDSA-AES128-SHA256      ECDH 256   AES        128       
xc013   ECDHE-RSA-AES128-SHA           ECDH 256   AES        128       
xc009   ECDHE-ECDSA-AES128-SHA         ECDH 256   AES        128       
x9c     AES128-GCM-SHA256              RSA        AESGCM     128       
x3c     AES128-SHA256                  RSA        AES        128       
x2f     AES128-SHA                     RSA        AES        128

Of interest is the browser and client simulated connections showing both RSA and ECDSA usage

Code (Text):

Running browser simulations (experimental)

Android 2.3.7                 TLSv1 AES128-SHA
Android 4.0.4                 TLSv1 ECDHE-RSA-AES128-SHA
Android 4.1.1                 TLSv1 ECDHE-RSA-AES128-SHA
Android 4.2.2                 TLSv1 ECDHE-RSA-AES128-SHA
Android 4.3                   TLSv1.0 ECDHE-RSA-AES128-SHA
Android 4.4.2                 TLSv1.1 ECDHE-RSA-AES128-SHA
Android 5.0.0                 TLSv1.2 ECDHE-ECDSA-CHACHA20-POLY1305
Baidu Jan 2015                TLSv1 ECDHE-RSA-AES128-SHA
BingPreview Jan 2015          TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
Chrome 47 / OSX               TLSv1.2 ECDHE-ECDSA-AES128-GCM-SHA256
Firefox 31.3.0ESR / Win7      TLSv1.2 ECDHE-ECDSA-AES128-GCM-SHA256
Firefox 42 / OSX              TLSv1.2 ECDHE-ECDSA-AES128-GCM-SHA256
GoogleBot Feb 2015            TLSv1.2 ECDHE-ECDSA-AES128-GCM-SHA256
IE6 / XP                      No connection
IE7 / Vista                   TLSv1.0 ECDHE-RSA-AES128-SHA
IE8 / XP                      No connection
IE8-10 / Win7                 TLSv1.0 ECDHE-RSA-AES128-SHA
IE11 / Win7                   TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
IE11 / Win8.1                 TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
IE10 / Win Phone 8.0          TLSv1.0 ECDHE-RSA-AES128-SHA
IE11 / Win Phone 8.1          TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
IE11 / Win Phone 8.1 Update   TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
IE11 / Win10                  TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
Edge 13 / Win10               TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
Edge 12 / Win Phone 10        TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
Java 6u45                     TLSv1 AES128-SHA
Java 7u25                     TLSv1 ECDHE-RSA-AES128-SHA
Java 8u31                     TLSv1.2 ECDHE-ECDSA-AES128-GCM-SHA256
OpenSSL 0.9.8y                TLSv1 AES128-SHA
OpenSSL 1.0.1l                TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
OpenSSL 1.0.2e                TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
Safari 5.1.9/ OSX 10.6.8      TLSv1 ECDHE-RSA-AES128-SHA
Safari 6 / iOS 6.0.1          TLSv1.2 ECDHE-ECDSA-AES256-SHA384
Safari 6.0.4/ OS X 10.8.4     TLSv1 ECDHE-RSA-AES128-SHA
Safari 7 / iOS 7.1            TLSv1.2 ECDHE-ECDSA-AES256-SHA384
Safari 7 / OS X 10.9          TLSv1.2 ECDHE-ECDSA-AES256-SHA384
Safari 8 / iOS 8.4            TLSv1.2 ECDHE-ECDSA-AES256-SHA384
Safari 8 / OS X 10.10         TLSv1.2 ECDHE-ECDSA-AES256-SHA384
Safari 9 / iOS 9              TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
Safari 9 / OS X 10.11         TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384

eva2000 · Jun 1, 2016

Confirmed that only OpenSSL 1.0.2+ support dual ECDSA + RSA certificates as LibreSSL doesn't support it Re: Multi certificate support returns Letsencrypt Intermediate Certificate twice

Only OpenSSL 1.0.2 and higher support separate chains for
different certificates. With older versions (including LibreSSL)
there is only one chain for all certificates, and all chained
certificates will be added to it. That is, if chains are the same
you have to leave only one of them.

--
Maxim Dounin
nginx news
Click to expand...

So if you want to use dual SSL certs with Centmin Mod Nginx 1.11 branch, you need to switch back from LibreSSL to OpenSSL 1.0.2 branch via setting /etc/centminmod/custom_config.inc with variable
Code (Text):
LIBRESSL_SWITCH='n'
then run centmin.sh menu option 4 to recompile Nginx

eva2000 · Jun 15, 2016

Setup dual ECDSA + RSA SSL certificate support for official centminmod.com site over HTTP/2 SSL for testing. Thought I'd just use a StartSSL 1yr DV SANs certs for ECDSA for now

setting /etc/centminmod/custom_config.inc with variable and running centmin.sh menu option 4 to recompile nginx 1.11.1 with OpenSSL 1.0.2h

Code (Text):

LIBRESSL_SWITCH='n'

nginx -V
nginx version: nginx/1.11.1
built by gcc 4.9.1 20140922 (Red Hat 4.9.1-10) (GCC)
built with OpenSSL 1.0.2h 3 May 2016
TLS SNI support enabled
configure arguments: --with-ld-opt='-ljemalloc -Wl,-z,relro -Wl,-rpath,/usr/local/lib' --with-cc-opt='-m64 -mtune=native -mfpmath=sse -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2' --sbin-path=/usr/local/sbin/nginx --conf-path=/usr/local/nginx/conf/nginx.conf --with-http_stub_status_module --with-http_secure_link_module --with-openssl-opt=enable-tlsext --add-module=../nginx-module-vts --with-libatomic --with-threads --with-stream=dynamic --with-stream_ssl_module --with-http_gzip_static_module --add-dynamic-module=../ngx_brotli --add-dynamic-module=../ngx_pagespeed-release-1.11.33.2-beta --with-http_sub_module --with-http_addition_module --with-http_image_filter_module=dynamic --with-http_geoip_module --with-http_realip_module --add-dynamic-module=../ngx-fancyindex-0.4.0 --add-module=../ngx_cache_purge-2.3 --add-module=../ngx_devel_kit-0.3.0 --add-module=../set-misc-nginx-module-0.30 --add-module=../echo-nginx-module-0.59 --add-module=../redis2-nginx-module-0.13 --add-module=../ngx_http_redis-0.3.7 --add-module=../lua-nginx-module-0.10.5 --add-module=../memc-nginx-module-0.17 --add-module=../srcache-nginx-module-0.31 --add-module=../headers-more-nginx-module-0.30 --with-pcre=../pcre-8.38 --with-pcre-jit --with-http_ssl_module --with-http_v2_module --with-openssl=../openssl-1.0.2h
Click to expand...

cipherscan output

Code (Text):

cipherscan https://centminmod.com     
....................................................................................
Target: centminmod.com:443

prio  ciphersuite                    protocols              pubkey_size  signature_algoritm       trusted  ticket_hint  ocsp_staple  pfs                 curves                                                                                                                                                curves_ordering
1     ECDHE-ECDSA-CHACHA20-POLY1305  TLSv1.2                256          sha256WithRSAEncryption  True     3600         False        ECDH,P-256,256bits  prime256v1                                                                                                                                            server
2     ECDHE-ECDSA-AES256-GCM-SHA384  TLSv1.2                256          sha256WithRSAEncryption  True     3600         False        ECDH,P-256,256bits  prime256v1                                                                                                                                            server
3     ECDHE-ECDSA-AES128-GCM-SHA256  TLSv1.2                256          sha256WithRSAEncryption  True     3600         False        ECDH,P-256,256bits  prime256v1                                                                                                                                            server
4     ECDHE-RSA-AES256-GCM-SHA384    TLSv1.2                2048         sha256WithRSAEncryption  True     3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1,brainpoolP256r1,secp256k1,sect571r1,sect571k1,sect409k1,sect409r1,sect283k1,sect283r1  server
5     ECDHE-RSA-AES128-GCM-SHA256    TLSv1.2                2048         sha256WithRSAEncryption  True     3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1,brainpoolP256r1,secp256k1,sect571r1,sect571k1,sect409k1,sect409r1,sect283k1,sect283r1  server
6     ECDHE-ECDSA-AES256-SHA384      TLSv1.2                256          sha256WithRSAEncryption  True     3600         False        ECDH,P-256,256bits  prime256v1                                                                                                                                            server
7     ECDHE-ECDSA-AES128-SHA256      TLSv1.2                256          sha256WithRSAEncryption  True     3600         False        ECDH,P-256,256bits  prime256v1                                                                                                                                            server
8     ECDHE-RSA-AES256-SHA384        TLSv1.2                2048         sha256WithRSAEncryption  True     3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1,brainpoolP256r1,secp256k1,sect571r1,sect571k1,sect409k1,sect409r1,sect283k1,sect283r1  server
9     ECDHE-RSA-AES128-SHA256        TLSv1.2                2048         sha256WithRSAEncryption  True     3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1,brainpoolP256r1,secp256k1,sect571r1,sect571k1,sect409k1,sect409r1,sect283k1,sect283r1  server
10    ECDHE-RSA-AES128-SHA           TLSv1,TLSv1.1,TLSv1.2  2048         sha256WithRSAEncryption  True     3600         False        ECDH,P-256,256bits  prime256v1,secp521r1,brainpoolP512r1,brainpoolP384r1,secp384r1,brainpoolP256r1,secp256k1,sect571r1,sect571k1,sect409k1,sect409r1,sect283k1,sect283r1  server
11    ECDHE-ECDSA-AES128-SHA         TLSv1,TLSv1.1,TLSv1.2  256          sha256WithRSAEncryption  True     3600         False        ECDH,P-256,256bits  prime256v1                                                                                                                                            server

OCSP stapling: not supported
Cipher ordering: server
Curves ordering: server - fallback: no
Server supports secure renegotiation
Server supported compression methods: NONE
TLS Tolerance: yes

ssllabs

Chrome

testssl run

Code (Text):

testlssl https://centminmod.com

 Testing protocols (via sockets except TLS 1.2, SPDY+HTTP2) 

 SSLv2      not offered (OK)
 SSLv3      not offered (OK)
 TLS 1      offered
 TLS 1.1    offered
 TLS 1.2    offered (OK)
 SPDY/NPN   h2, http/1.1 (advertised)
 HTTP2/ALPN h2, http/1.1 (offered)

 Testing ~standard cipher lists 

 Null Ciphers                 not offered (OK)
 Anonymous NULL Ciphers       not offered (OK)
 Anonymous DH Ciphers         not offered (OK)
 40 Bit encryption            not offered (OK)
 56 Bit encryption            not offered (OK)
 Export Ciphers (general)     not offered (OK)
 Low (<=64 Bit)               not offered (OK)
 DES Ciphers                  not offered (OK)
 Medium grade encryption      not offered (OK)
 Triple DES Ciphers           not offered (OK)
 High grade encryption        offered (OK)


 Testing robust (perfect) forward secrecy, (P)FS -- omitting Null Authentication/Encryption as well as 3DES and RC4 here 

 PFS is offered (OK)  ECDHE-ECDSA-AES256-GCM-SHA384 ECDHE-RSA-AES256-GCM-SHA384 ECDHE-ECDSA-CHACHA20-POLY1305 ECDHE-RSA-CHACHA20-POLY1305 ECDHE-RSA-AES256-SHA384 ECDHE-ECDSA-AES256-SHA384 ECDHE-ECDSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-ECDSA-AES128-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA ECDHE-ECDSA-AES128-SHA 


 Testing server preferences 

 Has server cipher order?     yes (OK)
 Negotiated protocol          TLSv1.2
 Negotiated cipher            ECDHE-ECDSA-CHACHA20-POLY1305, 256 bit ECDH
 Cipher order
    TLSv1:     ECDHE-RSA-AES128-SHA ECDHE-ECDSA-AES128-SHA
    TLSv1.1:   ECDHE-RSA-AES128-SHA ECDHE-ECDSA-AES128-SHA
    TLSv1.2:   ECDHE-ECDSA-CHACHA20-POLY1305 ECDHE-RSA-CHACHA20-POLY1305 ECDHE-ECDSA-AES256-GCM-SHA384 ECDHE-ECDSA-AES128-GCM-SHA256 ECDHE-RSA-AES256-GCM-SHA384 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-ECDSA-AES256-SHA384 ECDHE-ECDSA-AES128-SHA256 ECDHE-RSA-AES256-SHA384 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA ECDHE-ECDSA-AES128-SHA
    h2:        ECDHE-ECDSA-CHACHA20-POLY1305 
    http/1.1:  ECDHE-ECDSA-CHACHA20-POLY1305 


 Testing server defaults (Server Hello) 

 TLS extensions (standard)    "server name/#0" "renegotiation info/#65281" "EC point formats/#11" "session ticket/#35" "heartbeat/#15" "next protocol/#13172"
 Session Tickets RFC 5077     3600 seconds (PFS requires session ticket keys to be rotated <= daily)
 SSL Session ID support       yes
 TLS clock skew               random values, no fingerprinting possible 

  Server Certificate #1
   Signature Algorithm          SHA256 with RSA
   Server key size              RSA 2048 bits
   Fingerprint / Serial         SHA1 8CCB5CAA6066F2321A6FE8ED37920B7687CFBE39 / 623CBC1C62FD9C08BD83C9F033B009C8
                                SHA256 F9B041F7F6ACB1503FB68592B7F0B972D47683402DA2A5D30BAFCF9B70405E88
   Common Name (CN)             "*.centminmod.com" (wildcard certificate match) (works w/o SNI)
   subjectAltName (SAN)         "*.centminmod.com" "centminmod.com" 
   Issuer                       "COMODO RSA Domain Validation Secure Server CA" ("COMODO CA Limited" from "GB")
   EV cert (experimental)       no 
   Certificate Expiration       424 >= 60 days (2014-08-14 00:00 --> 2017-08-13 23:59 +0000)
   # of certificates provided   3
   Chain of trust (experim.)    "/usr/bin/etc/*.pem" cannot be found / not readable
   Certificate Revocation List  http://crl.comodoca.com/COMODORSADomainValidationSecureServerCA.crl
   OCSP URI                     http://ocsp.comodoca.com
   OCSP stapling                --

  Server Certificate #2
   Signature Algorithm          SHA256 with RSA
   Server key size              ECDSA 256 bits
   Fingerprint / Serial         SHA1 87AAA994F0DF040F2C4C37BBC8D595B4028B5A52 / 621E1C4A30678DA14EE76A441846173E
                                SHA256 37409279195B99CFD4DFBB06337D8AB228D3075D8FD0DBEAEAB446ED2BE44055
   Common Name (CN)             "centminmod.com" (works w/o SNI)
   subjectAltName (SAN)         "centminmod.com" "www.centminmod.com" "centminmod.net" "centmin.sh" "centmin.com" 
   Issuer                       "StartCom Class 1 DV Server CA" ("StartCom Ltd." from "IL")
   EV cert (experimental)       no 
   Certificate Expiration       364 >= 60 days (2016-06-15 10:10 --> 2017-06-15 10:10 +0000)
   # of certificates provided   2
   Chain of trust (experim.)    "/usr/bin/etc/*.pem" cannot be found / not readable
   Certificate Revocation List  http://crl.startssl.com/sca-server1.crl
   OCSP URI                     http://ocsp.startssl.com
   OCSP stapling                --


 Testing HTTP header response @ "/" 

 HTTP Status Code             200 OK
 HTTP clock skew              0 sec from localtime
 Strict Transport Security    --
 Public Key Pinning           --
 Server banner                nginx centminmod
 Application banner           X-Powered-By: centminmod
 Cookie(s)                    (none issued at "/")
 Security headers             X-Frame-Options: SAMEORIGIN
                              X-Xss-Protection: 1; mode=block
                              X-Content-Type-Options: nosniff
 Reverse Proxy banner         --


 Testing vulnerabilities 

 Heartbleed (CVE-2014-0160)                not vulnerable (OK)
 CCS (CVE-2014-0224)                       not vulnerable (OK)
 Secure Renegotiation (CVE-2009-3555)      not vulnerable (OK)
 Secure Client-Initiated Renegotiation     not vulnerable (OK)
 CRIME, TLS (CVE-2012-4929)                not vulnerable (OK)
 BREACH (CVE-2013-3587)                    potentially NOT ok, uses gzip HTTP compression. - only supplied "/" tested
                                           Can be ignored for static pages or if no secrets in the page
 POODLE, SSL (CVE-2014-3566)               not vulnerable (OK)
 TLS_FALLBACK_SCSV (RFC 7507), experim.    Downgrade attack prevention supported (OK)
 FREAK (CVE-2015-0204)                     not vulnerable (OK)
 DROWN (2016-0800, CVE-2016-0703), exper.  not vulnerable on this port (OK)
                                           make sure you don't use this certificate elsewhere with SSLv2 enabled services
                                           https://censys.io/ipv4?q=37409279195B99CFD4DFBB06337D8AB228D3075D8FD0DBEAEAB446ED2BE44055 SHA256 F9B041F7F6ACB1503FB68592B7F0B972D47683402DA2A5D30BAFCF9B70405E88 could help you to find out
 LOGJAM (CVE-2015-4000), experimental      not vulnerable (OK), common primes not checked. See below for any DH ciphers + bit size
 BEAST (CVE-2011-3389)                     TLS1: ECDHE-ECDSA-AES128-SHA ECDHE-RSA-AES128-SHA
                                           VULNERABLE -- but also supports higher protocols (possible mitigation): TLSv1.1 TLSv1.2
 RC4 (CVE-2013-2566, CVE-2015-2808)        no RC4 ciphers detected (OK)


 Testing all 183 locally available ciphers against the server, ordered by encryption strength 

Hexcode  Cipher Suite Name (OpenSSL)    KeyExch.   Encryption Bits
-------------------------------------------------------------------------
 xcc14   ECDHE-ECDSA-CHACHA20-POLY1305  ECDH 256   ChaCha20   256          
 xcc13   ECDHE-RSA-CHACHA20-POLY1305    ECDH 256   ChaCha20   256          
 xc030   ECDHE-RSA-AES256-GCM-SHA384    ECDH 256   AESGCM     256          
 xc02c   ECDHE-ECDSA-AES256-GCM-SHA384  ECDH 256   AESGCM     256          
 xc028   ECDHE-RSA-AES256-SHA384        ECDH 256   AES        256          
 xc024   ECDHE-ECDSA-AES256-SHA384      ECDH 256   AES        256          
 xc02f   ECDHE-RSA-AES128-GCM-SHA256    ECDH 256   AESGCM     128          
 xc02b   ECDHE-ECDSA-AES128-GCM-SHA256  ECDH 256   AESGCM     128          
 xc027   ECDHE-RSA-AES128-SHA256        ECDH 256   AES        128          
 xc023   ECDHE-ECDSA-AES128-SHA256      ECDH 256   AES        128          
 xc013   ECDHE-RSA-AES128-SHA           ECDH 256   AES        128          
 xc009   ECDHE-ECDSA-AES128-SHA         ECDH 256   AES        128          


 Running browser simulations (experimental) 

 Android 2.3.7                 No connection
 Android 4.0.4                 TLSv1 ECDHE-RSA-AES128-SHA
 Android 4.1.1                 TLSv1 ECDHE-RSA-AES128-SHA
 Android 4.2.2                 TLSv1 ECDHE-RSA-AES128-SHA
 Android 4.3                   TLSv1.0 ECDHE-RSA-AES128-SHA
 Android 4.4.2                 TLSv1.1 ECDHE-RSA-AES128-SHA
 Android 5.0.0                 TLSv1.2 ECDHE-ECDSA-CHACHA20-POLY1305
 Baidu Jan 2015                TLSv1 ECDHE-RSA-AES128-SHA
 BingPreview Jan 2015          TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 Chrome 47 / OSX               TLSv1.2 ECDHE-ECDSA-AES128-GCM-SHA256
 Firefox 31.3.0ESR / Win7      TLSv1.2 ECDHE-ECDSA-AES128-GCM-SHA256
 Firefox 42 / OSX              TLSv1.2 ECDHE-ECDSA-AES128-GCM-SHA256
 GoogleBot Feb 2015            TLSv1.2 ECDHE-ECDSA-AES128-GCM-SHA256
 IE6 / XP                      No connection
 IE7 / Vista                   TLSv1.0 ECDHE-RSA-AES128-SHA
 IE8 / XP                      No connection
 IE8-10 / Win7                 TLSv1.0 ECDHE-RSA-AES128-SHA
 IE11 / Win7                   TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 IE11 / Win8.1                 TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 IE10 / Win Phone 8.0          TLSv1.0 ECDHE-RSA-AES128-SHA
 IE11 / Win Phone 8.1          TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 IE11 / Win Phone 8.1 Update   TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 IE11 / Win10                  TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 Edge 13 / Win10               TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 Edge 12 / Win Phone 10        TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 Java 6u45                     No connection
 Java 7u25                     TLSv1 ECDHE-RSA-AES128-SHA
 Java 8u31                     TLSv1.2 ECDHE-ECDSA-AES128-GCM-SHA256
 OpenSSL 0.9.8y                No connection
 OpenSSL 1.0.1l                TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 OpenSSL 1.0.2e                TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 Safari 5.1.9/ OSX 10.6.8      TLSv1 ECDHE-RSA-AES128-SHA
 Safari 6 / iOS 6.0.1          TLSv1.2 ECDHE-ECDSA-AES256-SHA384
 Safari 6.0.4/ OS X 10.8.4     TLSv1 ECDHE-RSA-AES128-SHA
 Safari 7 / iOS 7.1            TLSv1.2 ECDHE-ECDSA-AES256-SHA384
 Safari 7 / OS X 10.9          TLSv1.2 ECDHE-ECDSA-AES256-SHA384
 Safari 8 / iOS 8.4            TLSv1.2 ECDHE-ECDSA-AES256-SHA384
 Safari 8 / OS X 10.10         TLSv1.2 ECDHE-ECDSA-AES256-SHA384
 Safari 9 / iOS 9              TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 Safari 9 / OS X 10.11         TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384

eva2000 · Sep 9, 2016

Sweet bug fix coming for dual certs Re: Multi Certificate Support with OCSP not working right
It looks like there is a bug which prevents nginx from using
different OCSP reponders when using OCSP stapling with multiple
certificates. It uses the responder from the last certificate in
the server{} block for all OCSP requests.

Please try the following patch:
Code (Text):
# HG changeset patch
# User Maxim Dounin <mdounin@mdounin.ru>
# Date 1473367064 -10800
# Thu Sep 08 23:37:44 2016 +0300
# Node ID 2037cc64cdceb5b8cb36103cdd9d00e05b8e7ec3
# Parent 4a16fceea03bde6653e05d337e87907f085535b3
OCSP stapling: fixed using wrong responder with multiple certs.

diff --git a/src/event/ngx_event_openssl_stapling.c 
b/src/event/ngx_event_openssl_stapling.c
--- a/src/event/ngx_event_openssl_stapling.c
+++ b/src/event/ngx_event_openssl_stapling.c
@@ -376,6 +376,7 @@ ngx_ssl_stapling_responder(ngx_conf_t *c
{
ngx_url_t u;
char *s;
+ ngx_str_t rsp;
STACK_OF(OPENSSL_STRING) *aia;

if (responder->len == 0) {
@@ -403,6 +404,8 @@ ngx_ssl_stapling_responder(ngx_conf_t *c
return NGX_DECLINED;
}

+ responder = &rsp;
+
responder->len = ngx_strlen(s);
responder->data = ngx_palloc(cf->pool, responder->len);
if (responder->data == NULL) {
--
Maxim Dounin
nginx news
Click to expand...

buik · Sep 10, 2016

eva2000 said: ↑

Sweet bug fix coming for dual certs Re: Multi Certificate Support with OCSP not working right
Click to expand...

Can't find this patch as official Nginx git commit.
What is the status of this patch?

eva2000 · Sep 10, 2016

It's a patch posted on forum/mailing list not in git

buik · Sep 10, 2016

eva2000 said: ↑

It's a patch posted on forum/mailing list not in git
Click to expand...

Can you confirm that this patch fixes the problem below;

It looks like there is a bug which prevents nginx from using
different OCSP reponders when using OCSP stapling with multiple
certificates
Click to expand...

?

buik · Sep 11, 2016

Bump this topic to come to the attention

eva2000 · Sep 11, 2016

haven't tried it yet though user in that post linked reports it works. Nginx 1.11.4 is due in less than 4 days so waiting for that first

buik · Sep 11, 2016

eva2000 said: ↑

haven't tried it yet though user in that post linked reports it works. Nginx 1.11.4 is due in less than 4 days so waiting for that first
Click to expand...

What do you think of Nginx 1.11/1.12 in general?
Useless release if you ask me.

Dual Certificate (RSA and ECC) support is the only interesting thing,
an extremely small feature and already ready for a long time.
It is clear to me that the Nginx team is stretching time. all the focus goes to plus.

Features as HTTP/2 push, which seem difficult to implement,
Nginx have not yet been started with, as they already should have started a long ago with this.

eva2000 · Sep 11, 2016

bassie said: ↑

What do you think of Nginx 1.11/1.12 in general?
Useless release if you ask me.
Click to expand...

not useless if the fixes and features added to 1.11 mainline are useful to you - just look at all the stream related improvements for HTTP/2 and TCP based load balancing nginx: log - i like

Ah reminds me need to start looking at adding all these new stream nginx modules ports from 1.11.4 into Centmin Mod 123.09beta01

Stream: realip module.

eva2000 · Sep 13, 2016

@bassie officially added patch fix OCSP stapling: fixed using wrong responder with multiple certs

buik · Sep 13, 2016

eva2000 said: ↑

haven't tried it yet though user in that post linked reports it works. Nginx 1.11.4 is due in less than 4 days so waiting for that first
Click to expand...

Patch is merged into Nginx source.
Edit. double post

eva2000 · Nov 12, 2016

Revisiting dual RSA+ECDSA SSL certificate support in Nginx 1.11 branch.

Fresh test subdomain.domain.com. Ensure subdomain.domain.com DNS A record has updated to point to server IP address and that you have recompiled or compiled Nginx with OpenSSL instead of LibreSSL, via LIBRESSL_SWITCH='n' set in /etc/centminmod/custom_config.inc and centmin.sh menu option 4 to recompile Nginx 1.11.5 or higher.

step 1. enable letsencrypt addons/acmetool.sh integration support in centmin mod 123.09beta01 via persistent config file variable LETSENCRYPT_DETECT='y' set in /etc/centminmod/custom_config.inc

step 2. Use centmin mod 123.09beta01 centmin.sh menu option 2 to set up Letsencrypt RSA 2048bit SSL certificate with either option 3 or 4

Code (Text):

Do you want to continue [y/n]: y

------------------------------------------------
You have 4 options:
------------------------------------------------
1. issue staging test cert with HTTP + HTTPS
2. issue staging test cert with HTTPS default
3. issue live cert with HTTP + HTTPS
4. issue live cert with HTTPS default
Enter option number 1-4: 3

step 3. Next is to manually obtain the 2nd Letsencrypt ECC 256bit ECDSA SSL certificate via addons/acmetool.sh manual mode which is 100% manual step instruction guide to use underlying acme.sh 3rd party Letsencrypt client installed by addons/acmetool.sh.

You need to temporarily override the addons/acmetool/sh default RSA 2048 bit SSL cert generation config via setting in persistent config file /etc/centminmod/custom_config.inc the ECC 256bit ECDSA ssl cert KEYLENGTH variable for the below manual option run only. Afterwards, remove the KEYLENGTH='ec-256' to go back to RSA 2048 bit SSL cert defaults if you want.

Code (Text):

KEYLENGTH='ec-256'

Code (Text):

/usr/local/src/centminmod/addons/acmetool.sh acmeupdate
/usr/local/src/centminmod/addons/acmetool.sh manual

The manual mode will give you instructions using subdomain.domain.com as example domain which you need to change all instances to yoursubdomain.domain.com. If using subdomain remove all instances of -d www.domain.com mentioned in manual instructions.

To get Letsencrypt ECC 256bit ECDSA SSL certificate via acme.sh commands

Code (Text):

/root/.acme.sh/acme.sh --force --issue -d subdomain.domain.com -w /home/nginx/domains/subdomain.domain.com/public -k ec-256 --useragent centminmod-centos7-acmesh-webroot --log /root/centminlogs/acmetool.sh-debug-log-121116-123310.log --log-level 2

At end of run you should get SSL cert output like

Code (Text):

[Sat Nov 12 12:35:00 UTC 2016] Your cert is in  /root/.acme.sh/subdomain.domain.com_ecc/subdomain.domain.com.cer
[Sat Nov 12 12:35:00 UTC 2016] Your cert key is in  /root/.acme.sh/subdomain.domain.com_ecc/subdomain.domain.com.key
[Sat Nov 12 12:35:01 UTC 2016] The intermediate CA cert is in  /root/.acme.sh/subdomain.domain.com_ecc/ca.cer
[Sat Nov 12 12:35:01 UTC 2016] And the full chain certs is there:  /root/.acme.sh/subdomain.domain.com_ecc/fullchain.cer

To install the SSL cert to /usr/local/nginx/conf/ssl/subdomain.domain.com/

Code (Text):

/root/.acme.sh/acme.sh --installcert -d subdomain.domain.com --certpath /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-acme-ecc.cer --keypath /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-acme-ecc.key --capath /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-acme-ecc.cer --reloadCmd /usr/bin/ngxreload --fullchainpath /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-fullchain-acme-ecc.key --ecc

So you'll end up with ssl cert files for ECC like

Code (Text):

ssl_certificate      /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-acme-ecc.cer;
ssl_certificate_key  /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-acme-ecc.key;
ssl_trusted_certificate /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-acme-ecc.cer;

step 4. Create a new concatenated file called /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-dualcert-rsa-ecc.cer which concatenates both the existing ssl_trusted_certificate created via centmin.sh menu option 2 and the one created manually for ECC 256 bit ECDSA certs

Code (Text):

cat /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-acme.cer /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-acme-ecc.cer > /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-dualcert-rsa-ecc.cer

step 5. edit include file called /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com.crt.key.conf which is contained in Nginx ssl vhost at /usr/local/nginx/conf/conf.d/subdomain.domain.com.ssl.conf

edit /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com.crt.key.conf to look like below, where first set of 4 files are created by centmin.sh menu option 2 and the last 4 files are manually created ones for ECC 256bit ECDSA SSL certificate

Code (Text):

  ssl_dhparam /usr/local/nginx/conf/ssl/subdomain.domain.com/dhparam.pem;
  ssl_certificate      /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-acme.cer;
  ssl_certificate_key  /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-acme.key;
  #ssl_trusted_certificate /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-acme.cer;

  ssl_certificate      /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-acme-ecc.cer;
  ssl_certificate_key  /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-acme-ecc.key;
  #ssl_trusted_certificate /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-acme-ecc.cer;
  ssl_trusted_certificate /usr/local/nginx/conf/ssl/subdomain.domain.com/subdomain.domain.com-dualcert-rsa-ecc.cer;

testssl check shows working correctly as browser simulations show some responding with ECDHE-RSA* or ECDHE-ECDSA* ssl ciphers for corresponding RSA 2048bit or ECC 256bit ECDSA ssl certificates or use ssllabs online test at SSL Server Test (Powered by Qualys SSL Labs)

Code (Text):

testssl subdomain.domain.com

No mapping file found

###########################################################
    testssl       2.8rc2 from https://testssl.sh/dev/
    (1.559 2016/10/15 20:55:22)

      This program is free software. Distribution and
             modification under GPLv2 permitted.
      USAGE w/o ANY WARRANTY. USE IT AT YOUR OWN RISK!

       Please file bugs @ https://testssl.sh/bugs/

###########################################################

 Testing protocols (via sockets except TLS 1.2, SPDY+HTTP2)

 SSLv2               not offered (OK)
 SSLv3               not offered (OK)
 TLS 1               offered
 TLS 1.1             offered
 TLS 1.2             offered (OK)
 Version tolerance   downgraded to TLSv1.2 (OK)
 SPDY/NPN            h2, http/1.1 (advertised)
 HTTP2/ALPN          h2, http/1.1 (offered)

 Testing ~standard cipher lists

 Null Ciphers                 not offered (OK)
 Anonymous NULL Ciphers       not offered (OK)
 Anonymous DH Ciphers         not offered (OK)
 40 Bit encryption            not offered (OK)
 56 Bit encryption            not offered (OK)
 Export Ciphers (general)     not offered (OK)
 Low (<=64 Bit)               not offered (OK)
 DES Ciphers                  not offered (OK)
 "Medium" grade encryption    not offered (OK)
 Triple DES Ciphers           not offered (OK)
 High grade encryption        offered (OK)


 Testing robust (perfect) forward secrecy, (P)FS -- omitting Null Authentication/Encryption as well as 3DES and RC4 here

 PFS is offered (OK)          ECDHE-ECDSA-AES128-GCM-SHA256 ECDHE-ECDSA-AES128-SHA256 ECDHE-ECDSA-AES128-SHA ECDHE-ECDSA-AES256-GCM-SHA384 ECDHE-ECDSA-AES256-SHA384 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA ECDHE-RSA-AES256-GCM-SHA384 ECDHE-RSA-AES256-SHA384
 Elliptic curves offered:     sect571r1 sect571k1 sect409k1 sect409r1 sect283k1 sect283r1 prime256v1 secp521r1 brainpoolP512r1 brainpoolP384r1 secp384r1 brainpoolP256r1 secp256k1

Code (Text):

 Testing server preferences

 Has server cipher order?     yes (OK)
 Negotiated protocol          TLSv1.2
 Negotiated cipher            ECDHE-ECDSA-AES256-GCM-SHA384, 256 bit ECDH
 Cipher order
    TLSv1:     ECDHE-RSA-AES128-SHA ECDHE-ECDSA-AES128-SHA
    TLSv1.1:   ECDHE-RSA-AES128-SHA ECDHE-ECDSA-AES128-SHA
    TLSv1.2:   ECDHE-ECDSA-AES256-GCM-SHA384 ECDHE-ECDSA-AES128-GCM-SHA256 ECDHE-RSA-AES256-GCM-SHA384 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-ECDSA-AES128-SHA256 ECDHE-ECDSA-AES256-SHA384 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES256-SHA384 ECDHE-RSA-AES128-SHA ECDHE-ECDSA-AES128-SHA
    h2:        ECDHE-ECDSA-AES256-GCM-SHA384 ECDHE-ECDSA-AES128-GCM-SHA256 ECDHE-RSA-AES256-GCM-SHA384 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-ECDSA-AES128-SHA256 ECDHE-ECDSA-AES256-SHA384 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES256-SHA384 ECDHE-RSA-AES128-SHA ECDHE-ECDSA-AES128-SHA
    http/1.1:  ECDHE-ECDSA-AES256-GCM-SHA384 ECDHE-ECDSA-AES128-GCM-SHA256 ECDHE-RSA-AES256-GCM-SHA384 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-ECDSA-AES128-SHA256 ECDHE-ECDSA-AES256-SHA384 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES256-SHA384 ECDHE-RSA-AES128-SHA ECDHE-ECDSA-AES128-SHA

Code (Text):

 Testing server defaults (Server Hello)

 TLS extensions (standard)    "server name/#0" "renegotiation info/#65281" "EC point formats/#11" "session ticket/#35" "heartbeat/#15" "application layer protocol negotiation/#16" "status request/#5" "next protocol/#13172"
 Session Tickets RFC 5077     3600 seconds (PFS requires session ticket keys to be rotated <= daily)
 SSL Session ID support       yes
 TLS clock skew               random values, no fingerprinting possible

  Server Certificate #1
   Signature Algorithm          SHA256 with RSA
   Server key size              RSA 2048 bits
   Fingerprint / Serial         SHA1 FFAAAEE9777D29D2CE2A77DDE279C8150B2780C / 038BB21AAAAA19F05EE130B27279F37
                                SHA256 8B72AAA01DD20F2D4A4CEA119E8C0BE5DA525FED13BE16D6E0606E693E8C3
   Common Name (CN)             "subdomain.domain.com" (CN in response to request w/o SNI: "subdomain.domain.com")
   subjectAltName (SAN)         "subdomain.domain.com"
   Issuer                       "Let's Encrypt Authority X3" ("Let's Encrypt" from "US")
   Trust (hostname)             Ok via SAN and CN (SNI mandatory)
   Chain of trust               "/usr/bin/etc/*.pem" cannot be found / not readable
   EV cert (experimental)       no
   Certificate Expiration       89 >= 30 days (2016-11-12 11:31 --> 2017-02-10 11:31 +0000)
   # of certificates provided   2
   Certificate Revocation List  --
   OCSP URI                     http://ocsp.int-x3.letsencrypt.org/
   OCSP stapling                offered

  Server Certificate #2
   Signature Algorithm          SHA256 with RSA
   Server key size              ECDSA 256 bits
   Fingerprint / Serial         SHA1 D71BF249D558EAAAA32AB72DB94299C32F221 / 03B2315AAAAA5C760F8CD2A706
                                SHA256 6F9A2E84A3AAAAAC9A681337FDB3329224C3865124CFAE3449
   Common Name (CN)             "subdomain.domain.com" (CN in response to request w/o SNI: "subdomain.domain.com")
   subjectAltName (SAN)         "subdomain.domain.com"
   Issuer                       "Let's Encrypt Authority X3" ("Let's Encrypt" from "US")
   Trust (hostname)             Ok via SAN and CN (SNI mandatory)
   Chain of trust               "/usr/bin/etc/*.pem" cannot be found / not readable
   EV cert (experimental)       no
   Certificate Expiration       89 >= 30 days (2016-11-12 11:35 --> 2017-02-10 11:35 +0000)
   # of certificates provided   2
   Certificate Revocation List  --
   OCSP URI                     http://ocsp.int-x3.letsencrypt.org/
   OCSP stapling                offered

Code (Text):

 Testing HTTP header response @ "/"

 HTTP Status Code             200 OK
 HTTP clock skew              0 sec from localtime
 Strict Transport Security    --
 Public Key Pinning           --
 Server banner                nginx centminmod
 Application banner           X-Powered-By: centminmod
 Cookie(s)                    (none issued at "/")
 Security headers             --
 Reverse Proxy banner         --

Code (Text):

 Testing vulnerabilities

 Heartbleed (CVE-2014-0160)                not vulnerable (OK)
 CCS (CVE-2014-0224)                       not vulnerable (OK)
 Secure Renegotiation (CVE-2009-3555)      not vulnerable (OK)
 Secure Client-Initiated Renegotiation     not vulnerable (OK)
 CRIME, TLS (CVE-2012-4929)                not vulnerable (OK)
 BREACH (CVE-2013-3587)                    potentially NOT ok, uses gzip HTTP compression. - only supplied "/" tested
                                           Can be ignored for static pages or if no secrets in the page
 POODLE, SSL (CVE-2014-3566)               not vulnerable (OK)
 TLS_FALLBACK_SCSV (RFC 7507),             Downgrade attack prevention supported (OK)
 FREAK (CVE-2015-0204)                     not vulnerable (OK)
 DROWN (2016-0800, CVE-2016-0703)          not vulnerable on this port (OK)
                                           make sure you don't use this certificate elsewhere with SSLv2 enabled services
                                           https://censys.io/ipv4?q=6F9A2EAAA80F1C2C9A681337FDB3329224C3865124CFAE3449 SHA256 8B7209ECFB01AAAAABE5DA525FED13BE16D6E0606E693E8C3 could help you to find out
 LOGJAM (CVE-2015-4000), experimental      not vulnerable (OK), common primes not checked. See below for any DH ciphers + bit size
 BEAST (CVE-2011-3389)                     TLS1: ECDHE-ECDSA-AES128-SHA ECDHE-RSA-AES128-SHA
                                           VULNERABLE -- but also supports higher protocols (possible mitigation): TLSv1.1 TLSv1.2
 RC4 (CVE-2013-2566, CVE-2015-2808)        no RC4 ciphers detected (OK)

Code (Text):

 Testing all 183 locally available ciphers against the server, ordered by encryption strength

Hexcode  Cipher Suite Name (OpenSSL)       KeyExch.  Encryption Bits
------------------------------------------------------------------------
 xc030   ECDHE-RSA-AES256-GCM-SHA384       ECDH 256   AESGCM    256
 xc02c   ECDHE-ECDSA-AES256-GCM-SHA384     ECDH 256   AESGCM    256
 xc028   ECDHE-RSA-AES256-SHA384           ECDH 256   AES       256
 xc024   ECDHE-ECDSA-AES256-SHA384         ECDH 256   AES       256
 xc02f   ECDHE-RSA-AES128-GCM-SHA256       ECDH 256   AESGCM    128
 xc02b   ECDHE-ECDSA-AES128-GCM-SHA256     ECDH 256   AESGCM    128
 xc027   ECDHE-RSA-AES128-SHA256           ECDH 256   AES       128
 xc023   ECDHE-ECDSA-AES128-SHA256         ECDH 256   AES       128
 xc013   ECDHE-RSA-AES128-SHA              ECDH 256   AES       128
 xc009   ECDHE-ECDSA-AES128-SHA            ECDH 256   AES       128

Code (Text):

 Running browser simulations via sockets (experimental)

 Android 2.3.7                 TLSv1.0 DHE-RSA-AES128-SHA
 Android 4.0.4                 TLSv1.0 ECDHE-RSA-AES128-SHA
 Android 4.1.1                 TLSv1.0 ECDHE-RSA-AES128-SHA
 Android 4.2.2                 TLSv1.0 ECDHE-RSA-AES128-SHA
 Android 4.3                   TLSv1.0 ECDHE-RSA-AES128-SHA
 Android 4.4.2                 TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 Android 5.0.0                 TLSv1.2 ECDHE-ECDSA-AES128-GCM-SHA256
 Baidu Jan 2015                TLSv1.0 ECDHE-RSA-AES128-SHA
 BingPreview Jan 2015          TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 Chrome 47 / OSX               TLSv1.2 ECDHE-ECDSA-AES128-GCM-SHA256
 Firefox 31.3.0ESR / Win7      TLSv1.2 ECDHE-ECDSA-AES128-GCM-SHA256
 Firefox 42 OS X               TLSv1.2 ECDHE-ECDSA-AES128-GCM-SHA256
 GoogleBot Feb 2015            TLSv1.2 ECDHE-ECDSA-AES128-GCM-SHA256
 IE 6 XP                       No connection
 IE 7 Vista                    TLSv1.0 ECDHE-RSA-AES128-SHA
 IE 8 XP                       No connection
 IE 8-10 Win 7                 TLSv1.0 ECDHE-RSA-AES128-SHA
 IE 11 Win 7                   TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 IE 11 Win 8.1                 TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 IE 10 Win Phone 8.0           TLSv1.0 ECDHE-RSA-AES128-SHA
 IE 11 Win Phone 8.1           TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 IE 11 Win Phone 8.1 Update    TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 IE 11 Win 10                  TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 Edge 13 Win 10                TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 Edge 13 Win Phone 10          TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 Java 6u45                     TLSv1.0 DHE-RSA-AES128-SHA
 Java 7u25                     TLSv1.0 ECDHE-RSA-AES128-SHA
 Java 8u31                     TLSv1.2 ECDHE-ECDSA-AES128-GCM-SHA256
 OpenSSL 0.9.8y                No connection
 OpenSSL 1.0.1l                TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 OpenSSL 1.0.2e                TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 Safari 5.1.9 OS X 10.6.8      TLSv1.0 ECDHE-RSA-AES128-SHA
 Safari 6 iOS 6.0.1            TLSv1.2 ECDHE-ECDSA-AES128-SHA256
 Safari 6.0.4 OS X 10.8.4      TLSv1.0 ECDHE-RSA-AES128-SHA
 Safari 7 iOS 7.1              TLSv1.2 ECDHE-ECDSA-AES128-SHA256
 Safari 7 OS X 10.9            TLSv1.2 ECDHE-ECDSA-AES128-SHA256
 Safari 8 iOS 8.4              TLSv1.2 ECDHE-ECDSA-AES128-SHA256
 Safari 8 OS X 10.10           TLSv1.2 ECDHE-ECDSA-AES128-SHA256
 Safari 9 iOS 9                TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
 Safari 9 OS X 10.11           TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384

 Done 2016-11-12 13:05:28    -->> ipaddress:443 (subdomain.domain.com) <<--

SSL Labs output

rdan · Dec 31, 2017

eva2000 said: ↑
Confirmed that only OpenSSL 1.0.2+ support dual ECDSA + RSA certificates as LibreSSL doesn't support it Re: Multi certificate support returns Letsencrypt Intermediate Certificate twice

So if you want to use dual SSL certs with Centmin Mod Nginx 1.11 branch, you need to switch back from LibreSSL to OpenSSL 1.0.2 branch via setting /etc/centminmod/custom_config.inc with variable
Code (Text):
LIBRESSL_SWITCH='n'
then run centmin.sh menu option 4 to recompile Nginx
Click to expand...
Latest libressl still doesn't support dual cert?

eva2000 · Jan 1, 2018

nope, only OpenSSL 1.0.2+

eva2000 · Jan 2, 2018

Revisiting dual rsa + ecdsa ssl cert deployment on my HTTP/2 HTTPS demo site for Centmin Mod 123.09beta01 at https://http2.centminmod.com using instructions outlined at SSL - Nginx 1.11.0 introduces dual ECDSA + RSA SSL certificate support ! Was motivated to revisit ECDSA SSL certs after seeing what Cloudflare's (Vlad Krasnov) contributed OpenSSL 1.1 branch patch did for improving ECDSA performance by up to 40+ %

Centmin Mod 123.09beta01 with Nginx 1.13.8 needs to use OpenSSL 1.0.2 or 1.1.0 branch for dual cert so set LIBRESSL_SWITCH='n' in persistent config file /etc/centminmod/custom_config.inc and recompile nginx via centmin.sh menu option 4 first.

nginx -V
nginx version: nginx/1.13.8
built by gcc 7.2.1 20170829 (Red Hat 7.2.1-1) (GCC)
built with OpenSSL 1.1.0g 2 Nov 2017
TLS SNI support enabled
configure arguments: --with-ld-opt='-L/usr/local/lib -ljemalloc -Wl,-z,relro -Wl,-rpath,/usr/local/lib' --with-cc-opt='-I/usr/local/include -m64 -march=native -DTCP_FASTOPEN=23 -g -O3 -fstack-protector-strong -flto -fuse-ld=gold --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wimplicit-fallthrough=0 -fcode-hoisting -Wp,-D_FORTIFY_SOURCE=2 -Wno-deprecated-declarations -gsplit-dwarf' --sbin-path=/usr/local/sbin/nginx --conf-path=/usr/local/nginx/conf/nginx.conf --with-compat --with-http_stub_status_module --with-http_secure_link_module --with-libatomic --with-http_gzip_static_module --add-dynamic-module=../ngx_brotli --add-dynamic-module=../ngx_pagespeed-1.13.35.1-beta --with-http_sub_module --with-http_addition_module --with-http_image_filter_module=dynamic --with-http_geoip_module --with-stream_geoip_module --with-stream_realip_module --with-stream_ssl_preread_module --with-threads --with-stream=dynamic --with-stream_ssl_module --with-http_realip_module --add-dynamic-module=../ngx-fancyindex-0.4.2 --add-module=../ngx_cache_purge-2.4.2 --add-module=../ngx_devel_kit-0.3.0 --add-dynamic-module=../set-misc-nginx-module-0.31 --add-dynamic-module=../echo-nginx-module-0.61 --add-module=../redis2-nginx-module-0.14 --add-module=../ngx_http_redis-0.3.7 --add-module=../memc-nginx-module-0.18 --add-module=../srcache-nginx-module-0.31 --add-dynamic-module=../headers-more-nginx-module-0.33 --with-pcre=../pcre-8.41 --with-pcre-jit --with-zlib=../zlib-cloudflare-1.3.0 --with-http_ssl_module --with-http_v2_module --with-openssl=../openssl-1.1.0g --with-openssl-opt='enable-ec_nistp_64_gcc_128'
Click to expand...

ssllabs test results confirm working dual rsa 2048 bit + ecdsa 256 bit ssl certs serving the correct cert to appropriately supported browser/web clients SSL Server Test: http2.centminmod.com (Powered by Qualys SSL Labs)

example chrome 49 on winxp sp3 doesn't support ECDSA ssl certs so falls back to RSA 2048bit cert using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

while chrome 57 on windows 7 supports ECDSA ssl cert so uses TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

ssl ciphers

eva2000 · Jan 3, 2018

Working with private test branch for addons/acmetool.sh with added dual RSA+ECDSA ssl certificate support out of the box when DUALCERTS='y' set in persistent config file.

Notes:

This updated code not available publicly yet so don't try it as it won't work.
This will involve 2 issuances so you'll run up to your letsencrypt rate limits faster (2x times faster if you use dual certs)

Using staging test letsencrypt ssl certificates so not hitting rate limits

Code (Text):

./acmetool.sh issue dualcert.domain.com

you'll notice a 2nd issuance/install cert call in output below

Code (Text):

./acmetool.sh issue dualcert.domain.com

-----------------------------------------------------------
issue & install letsencrypt ssl certificate for dualcert.domain.com
-----------------------------------------------------------
testcert value =
/root/.acme.sh/acme.sh --staging --issue -d dualcert.domain.com --days 60 -w /home/nginx/domains/dualcert.domain.com/public -k 2048 --useragent centminmod-centos7-acmesh-webroot --log /root/centminlogs/acmetool.sh-debug-log-030118-063303.log --log-level 2
[Wed Jan  3 06:33:48 UTC 2018] Using stage ACME_DIRECTORY: https://acme-staging.api.letsencrypt.org/directory
[Wed Jan  3 06:33:49 UTC 2018] Creating domain key
[Wed Jan  3 06:33:49 UTC 2018] The domain key is here: /root/.acme.sh/dualcert.domain.com/dualcert.domain.com.key
[Wed Jan  3 06:33:49 UTC 2018] Single domain='dualcert.domain.com'
[Wed Jan  3 06:33:49 UTC 2018] Getting domain auth token for each domain
[Wed Jan  3 06:33:49 UTC 2018] Getting webroot for domain='dualcert.domain.com'
[Wed Jan  3 06:33:49 UTC 2018] Getting new-authz for domain='dualcert.domain.com'
[Wed Jan  3 06:33:50 UTC 2018] The new-authz request is ok.
[Wed Jan  3 06:33:50 UTC 2018] dualcert.domain.com is already verified, skip http-01.
[Wed Jan  3 06:33:50 UTC 2018] Verify finished, start to sign.
[Wed Jan  3 06:33:50 UTC 2018] Cert success.
-----BEGIN CERTIFICATE-----
MIIE........

-----END CERTIFICATE-----
[Wed Jan  3 06:33:51 UTC 2018] Your cert is in  /root/.acme.sh/dualcert.domain.com/dualcert.domain.com.cer
[Wed Jan  3 06:33:51 UTC 2018] Your cert key is in  /root/.acme.sh/dualcert.domain.com/dualcert.domain.com.key
[Wed Jan  3 06:33:51 UTC 2018] The intermediate CA cert is in  /root/.acme.sh/dualcert.domain.com/ca.cer
[Wed Jan  3 06:33:51 UTC 2018] And the full chain certs is there:  /root/.acme.sh/dualcert.domain.com/fullchain.cer

get 2nd SSL cert issued for dual ssl cert config

/root/.acme.sh/acme.sh --staging --issue -d dualcert.domain.com --days 60 -w /home/nginx/domains/dualcert.domain.com/public -k ec-256 --useragent centminmod-centos7-acmesh-webroot --log /root/centminlogs/acmetool.sh-debug-log-030118-063303.log --log-level 2
[Wed Jan  3 06:33:51 UTC 2018] Using stage ACME_DIRECTORY: https://acme-staging.api.letsencrypt.org/directory
[Wed Jan  3 06:33:51 UTC 2018] Creating domain key
[Wed Jan  3 06:33:51 UTC 2018] The domain key is here: /root/.acme.sh/dualcert.domain.com_ecc/dualcert.domain.com.key
[Wed Jan  3 06:33:51 UTC 2018] Single domain='dualcert.domain.com'
[Wed Jan  3 06:33:51 UTC 2018] Getting domain auth token for each domain
[Wed Jan  3 06:33:51 UTC 2018] Getting webroot for domain='dualcert.domain.com'
[Wed Jan  3 06:33:51 UTC 2018] Getting new-authz for domain='dualcert.domain.com'
[Wed Jan  3 06:33:52 UTC 2018] The new-authz request is ok.
[Wed Jan  3 06:33:52 UTC 2018] dualcert.domain.com is already verified, skip http-01.
[Wed Jan  3 06:33:52 UTC 2018] Verify finished, start to sign.
[Wed Jan  3 06:33:53 UTC 2018] Cert success.
-----BEGIN CERTIFICATE-----
MIIEITCCAwm............
-----END CERTIFICATE-----
[Wed Jan  3 06:33:53 UTC 2018] Your cert is in  /root/.acme.sh/dualcert.domain.com_ecc/dualcert.domain.com.cer
[Wed Jan  3 06:33:53 UTC 2018] Your cert key is in  /root/.acme.sh/dualcert.domain.com_ecc/dualcert.domain.com.key
[Wed Jan  3 06:33:53 UTC 2018] The intermediate CA cert is in  /root/.acme.sh/dualcert.domain.com_ecc/ca.cer
[Wed Jan  3 06:33:53 UTC 2018] And the full chain certs is there:  /root/.acme.sh/dualcert.domain.com_ecc/fullchain.cer

success: 2nd SSL cert issued for dual ssl cert config

LECHECK = 0
  ssl_dhparam /usr/local/nginx/conf/ssl/dualcert.domain.com/dhparam.pem;
  ssl_certificate      /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme.cer;
  ssl_certificate_key  /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme.key;
  #ssl_trusted_certificate /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme.cer;

install segment

Code (Text):

-----------------------------------------------------------
install cert
-----------------------------------------------------------
/root/.acme.sh/acme.sh --installcert -d dualcert.domain.com --certpath /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme.cer --keypath /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme.key --capath /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme.cer --reloadCmd /usr/bin/ngxreload --fullchainpath /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-fullchain-acme.key
[Wed Jan  3 06:33:53 UTC 2018] Installing cert to:/usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme.cer
[Wed Jan  3 06:33:53 UTC 2018] Installing CA to:/usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme.cer
[Wed Jan  3 06:33:53 UTC 2018] Installing key to:/usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme.key
[Wed Jan  3 06:33:53 UTC 2018] Installing full chain to:/usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-fullchain-acme.key
[Wed Jan  3 06:33:53 UTC 2018] Run reload cmd: /usr/bin/ngxreload
Reloading nginx configuration (via systemctl):  [  OK  ]
[Wed Jan  3 06:33:53 UTC 2018] Reload success

install 2nd SSL cert issued for dual ssl cert config

/root/.acme.sh/acme.sh --installcert -d dualcert.domain.com --certpath /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme-ecc.cer --keypath /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme-ecc.key --capath /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme-ecc.cer --reloadCmd /usr/bin/ngxreload --fullchainpath /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-fullchain-acme-ecc.key --ecc
[Wed Jan  3 06:33:53 UTC 2018] Installing cert to:/usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme-ecc.cer
[Wed Jan  3 06:33:53 UTC 2018] Installing CA to:/usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme-ecc.cer
[Wed Jan  3 06:33:53 UTC 2018] Installing key to:/usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme-ecc.key
[Wed Jan  3 06:33:53 UTC 2018] Installing full chain to:/usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-fullchain-acme-ecc.key
[Wed Jan  3 06:33:53 UTC 2018] Run reload cmd: /usr/bin/ngxreload
Reloading nginx configuration (via systemctl):  [  OK  ]
[Wed Jan  3 06:33:54 UTC 2018] Reload success

letsencrypt ssl certificate setup completed
ssl certs located at: /usr/local/nginx/conf/ssl/dualcert.domain.com

the include file for dual ssl certs at /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com.crt.key.conf contents

Code (Text):

  ssl_dhparam /usr/local/nginx/conf/ssl/dualcert.domain.com/dhparam.pem;
  ssl_certificate      /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme.cer;
  ssl_certificate_key  /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme.key;

  ssl_certificate      /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme-ecc.cer;
  ssl_certificate_key  /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme-ecc.key;
 
  #ssl_trusted_certificate /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme.cer;
  #ssl_trusted_certificate /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme-ecc.cer;
  #ssl_trusted_certificate /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-dualcert-rsa-ecc.cer;

the dual cert concatenated ssl_trusted_certificate path is commented out for staging test letsencrypt ssl certs as it doesn't support OCSP stapling with untrusted test certs, only live letsencrypt ssl certs will have the path uncommented

Code (Text):

#ssl_trusted_certificate /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-dualcert-rsa-ecc.cer;

I also let the individual rsa and ecc ssl_trusted_certificate paths in include file commented out just in case you want to go back to single ssl cert

Code (Text):

  #ssl_trusted_certificate /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme.cer;
  #ssl_trusted_certificate /usr/local/nginx/conf/ssl/dualcert.domain.com/dualcert.domain.com-acme-ecc.cer;

Right now needs more testing in private copy of addons/acmetool.sh

pamamolf · Jan 4, 2018

What’s the benefit for using dual certificates?

Log in / Register

Forums

Join the community today

SSL Nginx 1.11.0 introduces dual ECDSA + RSA SSL certificate support !

eva2000 Administrator Staff Member

Nginx 1.11.0 dual ECDSA + RSA SSL Certificate Setup

Nginx 1.11.0 dual ECDSA + RSA SSL Certificate Tests

SSLLABS Tests

eva2000 Administrator Staff Member

cipherscan run

testssl run

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

buik “The best traveler is one without a camera.”

eva2000 Administrator Staff Member

buik “The best traveler is one without a camera.”

buik “The best traveler is one without a camera.”

eva2000 Administrator Staff Member

buik “The best traveler is one without a camera.”

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

buik “The best traveler is one without a camera.”

eva2000 Administrator Staff Member

rdan Well-Known Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

.

Log in / Register

Useful Searches

Join the community today

SSL Nginx 1.11.0 introduces dual ECDSA + RSA SSL certificate support !

eva2000 Administrator Staff Member

Nginx 1.11.0 dual ECDSA + RSA SSL Certificate Setup

Nginx 1.11.0 dual ECDSA + RSA SSL Certificate Tests

SSLLABS Tests

eva2000 Administrator Staff Member

cipherscan run

testssl run

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

buik “The best traveler is one without a camera.”

eva2000 Administrator Staff Member

buik “The best traveler is one without a camera.”

buik “The best traveler is one without a camera.”

eva2000 Administrator Staff Member

buik “The best traveler is one without a camera.”

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

buik “The best traveler is one without a camera.”

eva2000 Administrator Staff Member

rdan Well-Known Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

pamamolf Well-Known Member

.