Cloudflare Cloudflare You Get TLS 1.3 - out of beta

eva2000 · May 17, 2018

Cloudflare latest blog article regarding TLS 1.3 feature coming out of beta You get TLS 1.3! You get TLS 1.3! Everyone gets TLS 1.3!

With the specification finally nearing its official publication, and after several years of work (as well as 28 draft versions), we are happy to announce that the TLS 1.3 feature on Cloudflare is out of beta and will be enabled by default for all new zones.

For our Free and Pro customers not much changes, they already had TLS 1.3 enabled by default from the start. We have also decided to disable the 0-RTT feature by default for these plans (it was previously enabled by default as well), due to its inherent security properties. It will still be possible to explicitly enable it from the dashboard or the API (more on 0-RTT soon-ish in another blog post).

Our Business and Enterprise customers will now also get TLS 1.3 enabled by default for new zones (but will continue to have 0-RTT disabled). For existing Business customers that haven't made an explicit choice (that is, they haven't turned the feature on or off manually), we are also retroactively turning TLS 1.3 on.
Click to expand...

@bassie @Revenge interesting that Cloudflare can speak and support several TLS 1.3 drafts it seems ! (only TLS 1.3 draft 23 and draft 28)

It’s worth noting that the current Firefox beta (v61) switched to using draft 28, from draft 23 (which Chrome also uses). The two draft versions are incompatible due to some minor wire changes that were adopted some time after draft 23 was published, but Cloudflare can speak both versions so there won’t be a dip in adoption once Firefox 61 becomes stable. Once the final TLS 1.3 version (that is draft 28) becomes an official RFC we will also support that alongside the previous draft versions, to avoid leaving behind slow to update clients.
Click to expand...

From How do I enable TLS 1.3?

What is TLS 1.3?
TLS 1.3 is the newest and most secure version of the TLS protocol. It has improved latency over older versions and several new features.

What is 0-RTT?
0-RTT is a feature that improves performance for clients who have previously connected to your website. It allows the client's first request to be sent before the TLS connection is fully established, resulting in faster connection times.

What is the Early-Data header?
It's possible for an attacker to replay the first request sent with 0-RTT, this could result in Cloudflare sending the same requests multiple times to the origin. In order to help you identify when a request has been replayed, Cloudflare includes a new header named "Early-Data" on all requests that were sent over 0-RTT - the header will have a value of "1" in this case. You can use this header to make a decision on whether to accept a particular request sent during the 0-RTT connection phase.
Click to expand...

What should I do if I'm seeing an error/other issues while using TLS 1.3?

As TLS 1.3 implementations are fairly new, failures may occur. To help us debug our implementation, please submit a support ticket with steps to replicate the issue (if possible), client build version, client diagnostic information, and packet captures for our engineering team to review. Chrome users should submit a net-internals trace. Firefox users should report bugs to Mozilla and, if they determine that an issue is with our implementation, submit any logs they determine relevant to us.
Click to expand...

eva2000 · May 17, 2018

Looks like maybe Cloudflare TLS 1.3 only speaks TLS 1.3 draft 23 and draft 28 and not in between ?

Testing this forum which is behind Cloudflare with TLS 1.3 enabled and connecting with OpenSSL 1.1.1-pre6 binary which uses TLS 1.3 draft 26 IIRC shows the connection to Cloudflare is established over TLS 1.2 and not TLS 1.3

Code (Text):

/opt/openssl/bin/openssl version -a
OpenSSL 1.1.1-pre6 (beta) 1 May 2018
built on: Wed May 16 09:17:07 2018 UTC
platform: linux-x86_64
options:  bn(64,64) rc4(16x,int) des(int) idea(int) blowfish(ptr)
compiler: ccache gcc -fPIC -pthread -m64  -Wa,--noexecstack -Wall -O3 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPADLOCK_ASM -DPOLY1305_ASM -DNDEBUG
OPENSSLDIR: "/opt/openssl"
ENGINESDIR: "/opt/openssl/lib/engines-1.1"
Seeding source: os-specific

Code (Text):

echo -n | /opt/openssl/bin/openssl s_client -connect community.centminmod.com:443 -CAfile /etc/ssl/certs/cacert.pem| sed '/-----BEGIN CERTIFICATE-----/,/-----END CERTIFICATE-----/d' | sed '/Session-ID: /,/Verify return code/d'
depth=2 C = IE, O = Baltimore, OU = CyberTrust, CN = Baltimore CyberTrust Root
verify return:1
depth=1 C = US, ST = CA, L = San Francisco, O = "CloudFlare, Inc.", CN = CloudFlare Inc ECC CA-2
verify return:1
depth=0 C = US, ST = CA, L = San Francisco, O = "CloudFlare, Inc.", CN = centminmod.com
verify return:1
DONE
CONNECTED(00000003)
---
Certificate chain
 0 s:C = US, ST = CA, L = San Francisco, O = "CloudFlare, Inc.", CN = centminmod.com
   i:C = US, ST = CA, L = San Francisco, O = "CloudFlare, Inc.", CN = CloudFlare Inc ECC CA-2
 1 s:C = US, ST = CA, L = San Francisco, O = "CloudFlare, Inc.", CN = CloudFlare Inc ECC CA-2
   i:C = IE, O = Baltimore, OU = CyberTrust, CN = Baltimore CyberTrust Root
---
Server certificate
subject=C = US, ST = CA, L = San Francisco, O = "CloudFlare, Inc.", CN = centminmod.com

issuer=C = US, ST = CA, L = San Francisco, O = "CloudFlare, Inc.", CN = CloudFlare Inc ECC CA-2

Code (Text):

---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: ECDSA
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 2634 bytes and written 312 bytes
Verification: OK
---
New, TLSv1.2, Cipher is ECDHE-ECDSA-CHACHA20-POLY1305
Server public key is 256 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-ECDSA-CHACHA20-POLY1305
    Extended master secret: yes

eva2000 · May 17, 2018

Now testing older OpenSSL 1.1.1-pre2 client which uses TLS 1.3 draft 23 to connect

Code (Text):

/opt/openssl/bin/openssl version -a
OpenSSL 1.1.1-pre2 (alpha) 27 Feb 2018
built on: Thu Apr 26 19:14:23 2018 UTC
platform: linux-x86_64
compiler: ccache gcc -Wall -O3 -pthread -m64 -Wa,--noexecstack -DDSO_DLFCN -DHAVE_DLFCN_H -DNDEBUG -DOPENSSL_NO_STATIC_ENGINE -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DRC4_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPADLOCK_ASM -DPOLY1305_ASM -DOPENSSL_USE_NODELETE -DL_ENDIAN
OPENSSLDIR: "/opt/openssl"
ENGINESDIR: "/opt/openssl/lib/engines-1.1"
Seeding source: os-specific

shows TLS 1.3 connection established so Cloudflare only speaks TSL 1.3 draft 23 and draft 28. If you client, web browser etc only support TLS 1.3 drafts other than 23 or 28, you won't connect to Cloudflare with TLS 1.3 and use TLS 1.2 instead

Code (Text):

echo -n | /opt/openssl/bin/openssl s_client -connect community.centminmod.com:443 -CAfile /etc/ssl/certs/cacert.pem| sed '/-----BEGIN CERTIFICATE-----/,/-----END CERTIFICATE-----/d' | sed '/Session-ID: /,/Verify return code/d'
depth=2 C = IE, O = Baltimore, OU = CyberTrust, CN = Baltimore CyberTrust Root
verify return:1
depth=1 C = US, ST = CA, L = San Francisco, O = "CloudFlare, Inc.", CN = CloudFlare Inc ECC CA-2
verify return:1
depth=0 C = US, ST = CA, L = San Francisco, O = "CloudFlare, Inc.", CN = centminmod.com
verify return:1
DONE
CONNECTED(00000003)
---
Certificate chain
 0 s:C = US, ST = CA, L = San Francisco, O = "CloudFlare, Inc.", CN = centminmod.com
   i:C = US, ST = CA, L = San Francisco, O = "CloudFlare, Inc.", CN = CloudFlare Inc ECC CA-2
 1 s:C = US, ST = CA, L = San Francisco, O = "CloudFlare, Inc.", CN = CloudFlare Inc ECC CA-2
   i:C = IE, O = Baltimore, OU = CyberTrust, CN = Baltimore CyberTrust Root
---
Server certificate
subject=C = US, ST = CA, L = San Francisco, O = "CloudFlare, Inc.", CN = centminmod.com

issuer=C = US, ST = CA, L = San Francisco, O = "CloudFlare, Inc.", CN = CloudFlare Inc ECC CA-2

Code (Text):

---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: ECDSA
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 2545 bytes and written 402 bytes
Verification: OK
---
New, TLSv1.3, Cipher is TLS13-AES-256-GCM-SHA384
Server public key is 256 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
SSL-Session:
    Protocol  : TLSv1.3
    Cipher    : TLS13-AES-256-GCM-SHA384
    Extended master secret: no

buik · May 17, 2018

eva2000 said: ↑

@bassie @Revenge interesting that Cloudflare can speak and support several TLS 1.3 drafts it seems ! (only TLS 1.3 draft 23 and draft 28)
Click to expand...

eva2000 said: ↑

Looks like maybe Cloudflare TLS 1.3 only speaks TLS 1.3 draft 23 and draft 28 and not in between ?
Click to expand...

Yup and the reason is simple.
Chrome final is currently- on TLS 1.3 draft 23. Firefox is on TLS 1.3 draft 23.

Edge is on absolutely nothing.
Safari is on absolutely nothing, although there has been a test with TLS 1.3 draft 18.

As TLS 1.3 draft 28 is the one.
Supporting both draft 23 and draft 28 will catch all TLS 1.3 fish now and in the near feature.
No need to support in between.

eva2000 · May 17, 2018

Yeah just a matter of clients getting the right TLS 1.3 draft support.

For TLS 1.3 noobs

Next video is specific to F5 Big IP appliance servers - you can think of that as Nginx web server for our purposes

And TLS 1.3 and Perfect Forward Secrecy

eva2000 · Aug 11, 2018

@bassie A Detailed Look at RFC 8446 (a.k.a. TLS 1.3)

For the last five years, the Internet Engineering Task Force (IETF), the standards body that defines internet protocols, has been working on standardizing the latest version of one of its most important security protocols: Transport Layer Security (TLS). TLS is used to secure the web (and much more!), providing encryption and ensuring the authenticity of every HTTPS website and API. The latest version of TLS, TLS 1.3 (RFC 8446) was published today. It is the first major overhaul of the protocol, bringing significant security and performance improvements. This article provides a deep dive into the changes introduced in TLS 1.3 and its impact on the future of internet security.
Click to expand...

buik · Aug 12, 2018

eva2000 said: ↑

@bassie A Detailed Look at RFC 8446 (a.k.a. TLS 1.3)
Click to expand...

Thanks. Finally. Slow as@#$_&- mf@$_- at RFC

eva2000 · Aug 12, 2018

bassie said: ↑

Thanks. Finally. Slow as@#$_&- mf@$_- at RFC
Click to expand...

OpenSSL 1.1.1 roadmap [openssl-users] TLS 1.3 and the release

You probably know by now that TLS 1.3 was just released as RFC 8446; https://www.rfc-editor.org/info/rfc8446<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_info_rfc8446&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=2p92Jr9qHy6hkMg7JPW-TpAlWz_D-R8ocg6qkfLnRqg&m=sa62nNuYvx_z4e1BWAfP0k9YFTFWkgtt8hK1QfdOE2k&s=6_JEuDKb0eEPmTtlTG1zuEmDghQamc_PhPi16v8H-Tw&e=> This note is just trying to forestall a number of question threads.

Our release plan called for one final beta (there were various draft-interop things to take out and some other little nits) and then the official release. We have had no discussion of changing that plan.

Matt has already prepared a PR (the number escapes me), and there are a couple of open issues we still have to resolve. If all goes well, however, the final beta should begin very soon.

Thanks to everyone in the OpenSSL community for your help and support!
Click to expand...

and [openssl-users] [openssl-project] TLS 1.3 and the release

rsalz> Matt has already prepared a PR (the number escapes me)

WIP: Updates for RFC8446 (the final TLSv1.3 version) by mattcaswell · Pull Request #6741 · openssl/openssl
Click to expand...

Looks like from PR, openssl 1.1.1 plans to remove TLS 1.3 drafts 26, 27, 28 so would need for web browsers to update to TLS 1.3 final for openssl 1.1.1 to work.

buik · Aug 12, 2018

eva2000 said: ↑

Looks like from PR, openssl 1.1.1 plans to remove TLS 1.3 drafts 26, 27, 28 so would need for web browsers to update to TLS 1.3 final for openssl 1.1.1 to work.
Click to expand...

Don't worry.
Draft 28 is the one.

They will only remove the old drafts and the selection mechanism to switch between drafts. If your web-browser supports Draft 28 you are good to go.

eva2000 · Aug 14, 2018

Yeah It's official: TLS 1.3 approved as standard while spies weep

Work on 1.3 began in April 2014 and reached draft 28 before finally being approved in March this year. The protocol is so central to the encryption of internet traffic that it has taken until August 10 for engineers to check that nothing in it is going to cause any major problems.

The new version – which some argue could be called TLS 2.0 due to the significance of the changes – makes no less that three previous RFCs obsolete and updates another two. As things stand, there are currently no identified security holes in the algorithms used in TLS 1.3; the same cannot be said for 1.2.

And that points to the most critical part of the new RFC 8446: getting people to actually implement it.
Click to expand...

to 0-RTT or not ?

Hole in one?
If there is one downside it is concerns over the addition of a component called "0-RTT Resumption" which effectively allows the client and server to remember if they have spoken before, and so forego security checks, using previous keys to start talking immediately.

That will make connections much faster but opens up a potential security hole that those seeking to exploit TLS 1.3 will almost certainly focus on. The change was pushed by big tech companies like Google that will massively benefit from faster communications between its billions of connections, but some fear it will come back to bite everyone. Some companies are not implementing 0-RTT as a result.
Click to expand...

Log in / Register

Forums

Welcome to Centmin Mod Community

Cloudflare Cloudflare You Get TLS 1.3 - out of beta

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

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.”

eva2000 Administrator Staff Member

.

Log in / Register

Useful Searches

Welcome to Centmin Mod Community

Cloudflare Cloudflare You Get TLS 1.3 - out of beta

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

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.”

eva2000 Administrator Staff Member

.