Enable TLS 1.3 Encryption protocol, ultra-fast HTTPS experience

With the development of the Internet, the demand for the network speed is more and more high, especially in the case of vigorously developing HTTPS, the TLS encryption protocol becomes very important. And Pat the cloud in the popularization of HTTPS and performance optimization, always do their own efforts and contributions. At the beginning of 2018, the cloud CDN network was deployed with TLS 1.3, which further improved the user's access speed and security.

What is TLS 1.3?

The TLS 1.3 encryption protocol is an upgrade and retrofit on the basis of TLS 1.0, TLS 1.1, TLS 1.2, and is the biggest change to date, and the IETF is developing a new standard for TLS 1.3, which is now in the draft phase, and can refer to the latest draft. The main difference between TLS 1.3 and TLS 1.2 is that:

• The new cryptographic suite can only be used in TLS 1.3, and the old encryption suite cannot be used for TLS 1.3 connections;
• Added 0-rtt mode, which saves round-trip time (at the cost of some security) when establishing a connection;
• The static RSA (no forward secrecy) key exchange is abolished, and the key exchange mechanism based on public key can now provide forward secrecy;
• All handshake messages after Serverhello take the cryptographic action;
• The TLS 1.2 version of the renegotiation handshake mechanism has been deprecated and the renegotiation in TLS 1.3 becomes non-negotiable;
• Compared to the previous version, session recovery is stateless on the server, using a new PSK exchange;
• DSA certificates are no longer allowed for use in TLS 1.3;

These changes can avoid the previous version of the defect, not only this, but also reduce the TLS handshake time. To summarize, the TLS 1.3 has the following two major advantages over the previous version, namely:

• Faster speed of access
• Enhanced security

TLS 1.3 effect 1. Faster speed of access

To compare TLS 1.3 during the TLS handshake phase, the TLS 1.2 and TLS 1.3 are compared in the TLS handshake phase.

TLS 1.2 Full handshake framework (from RFC 5246)

As you can see, using TLS 1.2 requires two round trips (2-RTT) to complete the handshake before the request can be sent.

TLS 1.3 Full handshake framework (latest draft from TLS 1.3)

The handshake for TLS 1.3 no longer supports a static RSA key exchange, which means that a full handshake can be performed using a diffie-hellman with forward security. As you can see, using the TLS 1.3 protocol requires only one round trip (1-rtt) to complete the handshake.

The handshake time of TLS 1.3 is halved compared to TLS 1.2. This means that accessing a mobile website, using the TLS1.3 protocol, may reduce the time to nearly 100ms. The biggest change about 1-rtt is the elimination of serverkeyexchange and Clientkeyexchange messages, the DH parameter and the public key are now sent in a special key_share extension, which is a new extension type that will be included in the Client Hello and The Server Hello message.

TLS 1.3 0-rtt Mode Handshake Framework (latest draft from TLS 1.3)

It is worth noting that the 0 RTT (0-RTT) mode is added to the TLS 1.3 Draft, that is, in the last connection, after the handshake is completed, the server sends a SERVERCONFIGURATION message that initiates the first TLS record in the subsequent client ClientHello process , the encrypted application data is attached directly, which results in a faster access experience.

2. Enhanced Security

The development of TLS has a history of more than 20 years, in the previous version, TLS 1.2 is highly configurable, in order to better compatible with the older version of the browser, which means that those vulnerable sites are always running insecure encryption algorithms, which gives internet hackers an opportunity. TLS 1.3 Removes unsecured cryptographic algorithms based on previous versions, including:

• RSA Key Transfer--forward security not supported
• CBC mode password-susceptible to BEAST and Lucky 13 attacks
• RC4 Stream Password--not secure for use with HTTPS
• SHA-1 hash function--suggest replacing with SHA-2
• Any diffie-hellman group--cve-2016-0701 vulnerability
• Output password-vulnerable to FREAK and LogJam attacks

TLS 1.3 currently supports the following cryptographic suites:

tls13-aes128-gcm-sha256tls13-aes256-gcm-sha384tls13-chacha20-poly1305-sha256tls13- aes128-ccm-sha256tls13-aes128-ccm-8

The new cryptographic suite can only be used in TLS 1.3, and the old suite cannot be used for TLS 1.3 connections. In short, TLS 1.3 will be more secure than the old version of the TLS protocol, which also represents a major advance in Internet security.

At the beginning of 2018, and Pat the cloud in the CDN part of the node deployment of TLS 1.3, as the domestic earlier support for TLS 1.3 CDN vendors, and Pat Cloud always follow the pace of the Times, for the security and acceleration of the Internet world contribute their own strength. In the internet world of this ecosystem, the upgrade of TLS security protocol is not simple, this requires both the client and the server to upgrade at the same time, and ensure that all communication between the client and the server is normal.

One click to turn on TLS 1.31) on the cloud CDN platform enable TLS 1.3

On the Cloud CDN console, the switch is open for TLS 1.3, and TLS 1.3 is turned off by default, and you can turn it on manually, as shown in:

It is worth declaring whether the CDN is enabled for TLS 1.3, depending on whether the client browser supports it, and if the client does not support TLS 1.3, the protocol demotion will still be communicated using the lower TLS 1.2 protocol.

2) Enable TLS 1.3 in the browser

Currently the latest versions of Chrome and Firefox support TLS 1.3, but they all need to be turned on manually.

To manually enable TLS 1.3 in Firefox

Mozilla Firefox users can enable TLS 1.3 support in Firefox in the following ways (note that TLS 1.3 is supported by default in the Firfox nightly version, and Firefox stable (up to Firfox 57) needs to be specifically configured to Support for TLS 1.3).

• Enter About:config in the Firefox address bar. If a warning screen is displayed, make sure you are careful to ignore the security prompts;
• Search Security.tls.version.max in search area;
• Change the value of the preference item to 4 by double-clicking it (the default is 3).

Start TLS 1.3 Manually in Chrome

Google Chrome users can enable TLS 1.3 support in Chrome in the following ways (note that the Chrome Canary version supports TLS 1.3 by default, and Chrome stable (as of chrome 64) needs to be specifically configured to support T LS 1.3)

• Load chrome://flags/in the address bar of your browser, which opens the experiment page of your Web browser.
• Search for TLS or TLS in the search area, find the TLS 1.3 option, default
• You need to change TLS 1.3 to Enabled (Draft);
• Restart your Web browser.

Note: Versions prior to Chrome 62 need to change Maximum TLS version enabled to TLS 1.3.

Verify that TLS 1.3 is supported on the service side

Using the Google Chrome Developer tool, select the security module, as shown in, when the secure link is TLS 1.3, it means that the connection was communicated using TLS 1.3.

As you can tell, both the browser and the server support TLS 1.3 to communicate using TLS 1.3.

Summarize

TLS 1.3 is a great progress in WEB security and performance, although the mainstream browser has not been opened by default, but this day will not be too long, but also the pace of the cloud closely follow the times, hoping to provide Internet users with a more secure, faster acceleration experience, to promote the development of the Internet to contribute their own power. At the same time, we are also pleased to be the first CDN vendor to support the TLS 1.3 feature in China.

Recommended Reading

HTTPS series of Dry Goods (a): HTTPS principle of explanation

From HTTP to HTTPS to HSTS

Reference Documentation:

https://en.wikipedia.org/wiki/transport_layer_security

Https://www. Mitls.org/downloads/transcript-collisions.pdf

http://www. freebuf.com/vuls/95560. HTML

https://tools.ietf.org/html/draft-ietf-tls-tls13-23

https://tlswg.github.io/tls13-spec/#zero-rtt-exchange

https://blog.cloudflare.com/introducing-tls-1-3/

Https://www. openssl.org/blog/blog/2017/05/04/tlsv1.3/

Enable TLS 1.3 Encryption protocol, ultra-fast HTTPS experience