TLS 1.3 has been passed as a web standard by IETF and it comes with significant advancements. Learn how it could make our virtual world safer and faster.
3. 3
Why TLS 1.3?
LAUNCH Browser Support TLS 1.2 Improvement
Soon, TLS 1.3 will be adopted
by all leading browsers and
will soon become a reality
from the theoretical concept it
is.
Needless to say, TLS 1.3
brings a host of improvements
over TLS 1.2, the current
occupant of the SSL/TLS
family.
TLS 1.3, the latest and
unsurprisingly the most
advanced cryptographic
protocol till date, has finally
been approved by the IETF
(Internet Engineering Task
Force).
4. 4
SecureFaster
Why TLS 1.3 is Faster and Secure?
When it comes to browsing the internet, two things matter above else.
These things are security and speed.
TLS 1.3, with its faster handshake and security advancements, excels at both.
It sheds away the insecure skin of TLS 1.2 and its predecessors and offers a
quicker, secure way to communicate in the precarious world of internet.
6. 6
TLS 1.2 is not broken
TLS 1.2
TLS 1.2 Pitfalls
TLS 1.2 isn’t broken
TLS 1.3 with no Pitfalls
TLS 1.2 is broken. It’s
definitely not broken.
TLS 1.3 eliminates such
possibility as it doesn’t consist
of such obsolete components.
TLS 1.2, with all its benefits
and successful serving tenure,
has its pitfalls.
These pitfalls come in the
form of insecure protocols,
ciphers, and algorithms.
7. 7
RC4 Steam Cipher CBC Mode CiphersSHA-1 Hash Function Various Diffie-Hellman groups
3DES MD5 AlgorithmDES RSA Key Transport
Ciphers & Protocols of its predecessors abandoned by TLS 1.3
EXPORT-strength ciphers
8. 8
Less traveling = More speed
TLS Handshake Encrypted communication
This handshake involves a
series of back-and-forth
communication and verification
steps between both entities.
During these steps, they come to terms of
data transfer and pave the way for
encrypted communication.
As good as this sounds, it comes with a
constraint – SPEED.
For a TLS-enabled secure
connection to take place, a
process named ‘TLS
handshake’ must take place
between the client and the
server.
9. 9
As a result, it takes a bit more time to perform the
handshake and establish a secure connection.
The TLS 1.2 handshake incorporates two round-
trips of communication between server and
client.
To give you a number, it takes around 0.25 to 0.5
seconds for it.
This may not look like a lot on paper, but it can
make some serious difference in reality as the
data transfer takes place after the handshake.
TLS 1.2 handshake
10. 10
TLS 1.3 introduces 1-RTT handshake that cuts
the handshake time by almost half.
With TLS 1.3, we’re about to see a radical
change in the handshake time.
In areas where even a microsecond can make a world of
a difference, this is nothing less than a boon.
As good as the 1-RTT handshake is, it’s 0-RTT
Resumption that has stolen the thunder from it.
TLS 1.3 handshake
11. 11
If the server and client have come across each other before, the
handshake will be of zero round-trips. 0-RTT Resumption is
accomplished by using the stored information such as session IDs.
Yes, a handshake consisting of zero round-trips!
This takes the handshake time down to the bottom.
This way unprecedented connection speed will
be achieved with the introduction of TLS 1.3.
TLS 1.3 handshake
12. 12
Step Client Direction Message Direction Server
1
Client Hello
Support Cipher Suites
Guesses Key Agreement Protocol
Key Share
2
Server Hello
Key Agreement Protocol
Key Share
Server Finished
3 Check Certificate
Generates Key
Client Finished
Image: TLS 1.3 handshake Process
13. 13
Thankfully, it’s been passed
by IETF, and it’s become a
question of ‘when’ instead of
‘if.’
Thanks to IETF
There’s no doubt about the
fact that the internet will be a
better place when TLS 1.3
arrives.
Welcome TLS 1.3
Keep following our blog to
keep your pulse on TLS 1.3
and all significant changes
happening within the SSL
industry. Sayonara!
Follow us for More
Conclusion
TLS 1.3 is the best Encryption Protocol till date
14. 14
• SSL Vs TLS: What No One Tells You About!
• 3 Ways to Bolster Your SSL/TLS Security
• TLS 1.3 is now active in Firefox
Resources