NGINX only enabling TLS1.2 ?

Eric Germann ekgermann at
Wed Apr 18 01:01:03 UTC 2018

Piling on this, I built nginx-1.14.0 from source with openssl-1.1.1-pre5 compiled in.

The macro in the header says it’s at TLS 1.3 Draft 26

Chrome 66 claims to support Draft 23 (via chrome://flags <chrome://flags>)?

Neither Cloudflare nor Chrome report TLS 1.3

Yet when I do this from the command line for testing (openssl s_client host:443 <>)

I get

New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 384 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
    Protocol  : TLSv1.3
    Cipher    : TLS_AES_256_GCM_SHA384

ssl_ciphers are set to


My questions:

1.	Do the drafts try to negotiate to a common draft?

2.	the server is compiled statically to the source for openssl that the openssl command is executed from.  I’d think they would be able to negotiate the first protocol listed.

3.	Why does the protocol come up (even with the openssl command) as TLS_AES_256_GCM_SHA384 and not the TLS13 variants?  ChaCha20-Poly1305 works in TLS1.2 just fine.



> On Apr 17, 2018, at 1:45 PM, Reinis Rozitis <r at <mailto:r at>> wrote:
>> Is there any reason why SSLlabs would report only 1.2 as being available despite the config showing otherwise ?
> Also SSLLabs supports only tls 1.3 draft18 while for example OpenSSL 1.1.1pre4 is draft 28, so it won't show that the server supports tls1.3.
> rr
> _______________________________________________
> nginx mailing list
> nginx at <mailto:nginx at>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <>

More information about the nginx mailing list